Inspect specific parts of the current system editor state in detail. Unlike find_system (which looks up the saved server-side system), this inspects the current unsaved system editor state in the sidebar.
AI agents call inspect_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 tool retrieves or queries internal system editor state details without side effects. It does not create, modify, delete, or execute operations—it only provides visibility into the current unsaved state of the system editor in the sidebar. This is a classic Read operation with minimal risk.
From the tool's definition Tool description states it 'inspects' and 'looks up' system editor state, with explicit contrast to find_system suggesting query/retrieval semantics. The term 'inspect' indicates passive observation of current state without modification.
Documented attack patterns abuse exactly the kind of access inspect_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 inspect_system:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_system": {}
}
}inspect_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.
Inspect specific parts of the current system editor state in detail. Unlike find_system (which looks up the saved server-side system), this inspects the current unsaved system editor state in the sidebar. 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_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.
inspect_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 inspect_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 inspect_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.
inspect_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.