Look up a saved role by ID, or list all roles. Returns the persisted role configuration (not the current UI draft). Use inspect_role for the current draft state.
AI agents call find_role 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.
The tool performs lookups and listing operations that retrieve data about role configurations. It explicitly returns persisted configuration without making changes, executing code, or affecting system state. This is a standard Read category operation. Severity is low because disclosing role configurations, while potentially informative to an attacker, does not directly enable unauthorized actions on its own.
From the tool's definition Tool description states 'Look up a saved role by ID, or list all roles' and 'Returns the persisted role configuration'. These are query/retrieval operations with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access find_role 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_role:
{
"version": "1",
"default": "deny",
"tools": {
"find_role": {}
}
}find_role 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 a saved role by ID, or list all roles. Returns the persisted role configuration (not the current UI draft). Use inspect_role for the current draft state. 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_role: 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_role 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_role 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_role. 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_role 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.