Persists a draft tool to the database. Requires a draftId from build_tool. After saving, the tool can be executed by ID using run_tool with toolId.
AI agents use save_tool to create or update resources in Superglue MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superglue MCP environment.
This tool writes data (a tool definition) to a database, reversibly. It does not execute arbitrary code directly (that occurs via run_tool later), nor does it delete or move money.
From the tool's definition Tool description states 'Persists a draft tool to the database' — this is a create/write operation that durably stores a tool definition.
Documented attack patterns abuse exactly the kind of access save_tool 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 save_tool:
{
"version": "1",
"default": "deny",
"tools": {
"save_tool": {
"limits": [
{
"counter": "save_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Persists a draft tool to the database. Requires a draftId from build_tool. After saving, the tool can be executed by ID using run_tool with toolId. It is categorised as a Write tool in the Superglue MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Superglue MCP server in PolicyLayer and add a rule for save_tool: 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.
save_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_tool 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 save_tool. 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.
save_tool 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.