Look up an existing system by ID or search by query. Also returns system knowledge (OAuth config, documentation URL) for systems not yet created. Use
AI agents call find_system 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 is a straightforward data retrieval operation. While it exposes system metadata including OAuth configuration details, it does not create, modify, delete, or execute any code. The disclosure of OAuth config information is informational rather than operationally sensitive in this context, as actual authentication/token handling is separate (handled by authenticate and authenticate_oauth tools).
From the tool's definition 'Look up an existing system by ID or search by query' — retrieves system metadata and knowledge without modifying, creating, or deleting. Returns OAuth config and documentation URLs as informational data.
Documented attack patterns abuse exactly the kind of access find_system 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_system:
{
"version": "1",
"default": "deny",
"tools": {
"find_system": {}
}
}find_system 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 system by ID or search by query. Also returns system knowledge (OAuth config, documentation URL) for systems not yet created. 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_system: 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_system 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_system 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_system. 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_system 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.