AI agents call typesense_query to retrieve information from Typesense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool querying a search index is a read-only operation that retrieves data without modifying, deleting, or executing external commands. Even if query parameters are user-controlled, Typesense queries return search results rather than executing arbitrary code. The low severity reflects minimal blast radius—misuse returns unwanted data but causes no destructive or financial harm.
From the tool's definition Tool name 'typesense_query' and server description stating it enables 'search, and analyze data stored in Typesense collections through tools for querying documents' indicates a query/search operation.
Documented attack patterns abuse exactly the kind of access typesense_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Typesense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for typesense_query:
{
"version": "1",
"default": "deny",
"tools": {
"typesense_query": {}
}
}typesense_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
typesense_query. It is categorised as a Read tool in the Typesense MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Typesense MCP Server MCP server in PolicyLayer and add a rule for typesense_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 Typesense MCP Server. Nothing to install.
typesense_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 typesense_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 typesense_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.
typesense_query is provided by the Typesense MCP Server MCP server (suhail-ak-2/mcp-typesense-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Typesense MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Typesense MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.