Normalize user text before retrieval, routing, or agent planning.
AI agents call normalize_user_query to retrieve information from AI App MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs query normalization (text preprocessing) to prepare user input for downstream operations like search or routing. It retrieves no data, modifies no persistent state, executes no external commands, and produces no irreversible changes. It is a pure transformation utility, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it 'normalize[s] user text before retrieval, routing, or agent planning' — a text processing operation with no side effects on stored data or external systems.
Attacks that exploit this kind of access
Normalize user text before retrieval, routing, or agent planning. It is categorised as a Read tool in the AI App MCP MCP Server, which means it retrieves data without modifying state.
Register the AI App MCP server in PolicyLayer and add a rule for normalize_user_query: 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 AI App MCP. Nothing to install.
normalize_user_query 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 normalize_user_query 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 normalize_user_query. 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.
normalize_user_query is provided by the AI App MCP server (yh008/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 →