AI agents call wordpress_list_font_faces to retrieve information from ItchWPMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates font metadata from WordPress's Font Library. It has no side effects—it does not create, modify, delete, or execute operations. The data returned is informational only. The low severity reflects minimal blast radius; misuse would at worst return unwanted font information, with no capability to alter system state or commit harmful actions.
From the tool's definition The tool name 'list' and description 'List font face variations' indicate a query operation that retrieves data from the WordPress Font Library without modification. The parameters requested are read-only attributes (weight, style, src).
Attacks that exploit this kind of access
List font face variations (weight, style, src) for a specific font family from the WordPress Font Library. It is categorised as a Read tool in the ItchWPMCP MCP Server, which means it retrieves data without modifying state.
Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_list_font_faces: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ItchWPMCP. Nothing to install.
wordpress_list_font_faces is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wordpress_list_font_faces rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for wordpress_list_font_faces. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
wordpress_list_font_faces is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →