sanitize_query
AI agents use sanitize_query to create or update resources in Query Sanitizer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Query Sanitizer environment.
Based on the server description, sanitize_query likely redacts/transforms input text by replacing sensitive data with placeholders before forwarding to external LLMs. This is a data modification operation (Write) — it alters the content reversibly (placeholders can be restored via 'restore_response').
From the tool's definition Tool name: 'sanitize_query'; server description mentions 'sanitize queries' and 'redacts sensitive information from prompts using local models'
Attacks that exploit this kind of access
sanitize_query. It is categorised as a Write tool in the Query Sanitizer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Query Sanitizer MCP server in PolicyLayer and add a rule for sanitize_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 Query Sanitizer. Nothing to install.
sanitize_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sanitize_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 sanitize_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.
sanitize_query is provided by the Query Sanitizer MCP server (vidoluco/query-sanitizer-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 →