Builds a new superglue tool by accepting the full tool configuration JSON. Successful builds are auto-saved — use the returned toolId for all subsequent operations. In the tool playground, builds remain draft-only until explicitly saved.
AI agents use build_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 creates a new tool/resource in the system and auto-saves it, making it a Write operation (reversible creation). It doesn't execute code directly, delete data, or involve financial transactions. The severity is medium because a malicious agent could create harmful or unauthorized tool configurations that could be used in subsequent operations.
From the tool's definition 'Builds a new superglue tool by accepting the full tool configuration JSON' and 'Successful builds are auto-saved'
Documented attack patterns abuse exactly the kind of access build_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 build_tool:
{
"version": "1",
"default": "deny",
"tools": {
"build_tool": {
"limits": [
{
"counter": "build_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}build_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.
Builds a new superglue tool by accepting the full tool configuration JSON. Successful builds are auto-saved — use the returned toolId for all subsequent operations. In the tool playground, builds remain draft-only until explicitly saved. 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 build_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.
build_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 build_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 build_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.
build_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.