Look up an existing tool by ID or search for tools by query. Use
AI agents call find_tool to retrieve information from Superglue MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about existing tools in the Superglue system. It is a read-only query operation that returns information without side effects, state changes, or code execution. The search and lookup functions are classic Read operations. Severity is low because discovering available tools poses minimal risk even if an AI agent queries broadly, as no data is modified, deleted, or executed.
From the tool's definition Tool description states 'Look up an existing tool by ID or search for tools by query' — explicitly a lookup/search operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access find_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Superglue MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_tool:
{
"version": "1",
"default": "deny",
"tools": {
"find_tool": {}
}
}find_tool 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.
Look up an existing tool by ID or search for tools by query. Use. It is categorised as a Read tool in the Superglue MCP MCP Server, which means it retrieves data without modifying state.
Register the Superglue MCP server in PolicyLayer and add a rule for find_tool: 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 Superglue MCP. Nothing to install.
find_tool 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 find_tool 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 find_tool. 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.
find_tool is provided by the Superglue MCP server (superglue-ai/superglue). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Superglue MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Superglue MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.