Read the current role configuration draft. Returns tool permissions, system access levels (with inline custom rules), members assigned to this role, and lists of available tools/systems.
AI agents call inspect_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.
This tool retrieves and queries role configuration metadata (permissions, access levels, members, available tools/systems) without modifying, deleting, or executing any operations. It is a read-only inspection operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'inspect_role' and description 'Read the current role configuration draft. Returns tool permissions, system access levels..., members assigned to this role, and lists of available tools/systems.' - the verb 'Read' and 'Returns' indicate data…
Documented attack patterns abuse exactly the kind of access inspect_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 inspect_role:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_role": {}
}
}inspect_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.
Read the current role configuration draft. Returns tool permissions, system access levels (with inline custom rules), members assigned to this role, and lists of available tools/systems. 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 inspect_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.
inspect_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 inspect_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 inspect_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.
inspect_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.