wp_get_term_meta tool reference for StifLi Flex MCP
Sensitive readgets term metadata and redacts values that look like secrets. Output is structured as `{term_id, key, value}` when `meta_key` is provided, or `{term_id, meta}` when it is not.
Description
gets term metadata and redacts values that look like secrets. Output is structured as `{term_id, key, value}` when `meta_key` is provided, or `{term_id, meta}` when it is not.
What it is for
- Diagnosing taxonomies enriched by plugins.
Example use case
debugging custom term fields.
Sample prompt
Get term meta for term ID 77 and return both the structured output and redacted values so I can inspect plugin data safely.
Sample response
{
"tool": "wp_get_term_meta",
"status": "ok",
"items": []
}
What does wp_get_term_meta do?
gets term metadata and redacts values that look like secrets. Output is structured as `{term_id, key, value}` when `meta_key` is provided, or `{term_id, meta}` when it is not.
Does wp_get_term_meta modify site data?
It does not modify data, but it can expose sensitive site, user, or configuration details.
Which capability is commonly required?
It usually runs under controls compatible with manage_categories and the active MCP profile.
How should wp_get_term_meta be used safely?
Restrict this tool by profile and avoid exposing full raw output in shared channels.