Fetches recent run history for saved tools. Draft executions (build_tool, run_tool with draftId) do NOT create runs — errors are in the tool result directly. Set fetchResults=true only when investigating, not when listing runs.
AI agents call get_runs 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 queries and retrieves historical execution data without modifying, deleting, or triggering any actions. It is purely informational. The note about fetchResults warns against overuse for performance reasons, but does not change the fundamental read-only nature of the operation.
From the tool's definition Tool name is 'get_runs' and description states it 'Fetches recent run history for saved tools' — a read-only retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_runs 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 get_runs:
{
"version": "1",
"default": "deny",
"tools": {
"get_runs": {}
}
}get_runs 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.
Fetches recent run history for saved tools. Draft executions (build_tool, run_tool with draftId) do NOT create runs — errors are in the tool result directly. Set fetchResults=true only when investigating, not when listing runs. 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 get_runs: 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.
get_runs 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 get_runs 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 get_runs. 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.
get_runs 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.