AI agents call search_text to retrieve information from Allcanuse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_text' strongly suggests searching or querying text content without modification. In the absence of a descriptive definition, the read-only semantic of 'search' is the most reasonable interpretation. However, confidence is moderate (0.7) rather than high because the empty description prevents confirmation that this tool does not perform writes, executions, or other side effects.
From the tool's definition Tool name 'search_text' indicates a text search operation with no description provided. Based on naming convention alone, this appears to be a read-only query function.
Documented attack patterns abuse exactly the kind of access search_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for search_text:
{
"version": "1",
"default": "deny",
"tools": {
"search_text": {}
}
}search_text 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.
search_text. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
Register the Allcanuse MCP server in PolicyLayer and add a rule for search_text: 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 Allcanuse. Nothing to install.
search_text 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 search_text 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 search_text. 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.
search_text is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, 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.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.