AI agents call get_ux_taxonomy to retrieve information from Blop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-computed static UX taxonomy information from a cache. The emphasis on 'static', 'cached', and 'small JSON' confirms it is a pure read operation that queries configuration or metadata without modifying state, executing code, or triggering external effects. The low blast radius reflects that misuse would only expose or retrieve planning metadata, not enable destructive or financial actions.
From the tool's definition Tool name 'get_ux_taxonomy' and description 'Static UX/criticality hints for planning (cached, small JSON)' indicate retrieval of cached, read-only data with no mutations or side effects.
Attacks that exploit this kind of access
Static UX/criticality hints for planning (cached, small JSON). It is categorised as a Read tool in the Blop MCP Server, which means it retrieves data without modifying state.
Register the Blop MCP server in PolicyLayer and add a rule for get_ux_taxonomy: 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 Blop. Nothing to install.
get_ux_taxonomy 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 get_ux_taxonomy 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 get_ux_taxonomy. 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.
get_ux_taxonomy is provided by the Blop MCP server (n2400813g/blop-mcp). 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 →