Registers a new tool provider by providing its call template.
AI agents use register_manual to create or update resources in UTCP-MCP Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UTCP-MCP Bridge environment.
This tool creates a new registration entry for a tool provider, which is a reversible write operation. However, it carries high severity because registering a malicious or rogue tool provider could expose the MCP bridge to arbitrary external tools, potentially enabling subsequent Execute or Destructive actions through the newly registered provider.
From the tool's definition "Registers a new tool provider by providing its call template"
Documented attack patterns abuse exactly the kind of access register_manual gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UTCP-MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for register_manual:
{
"version": "1",
"default": "deny",
"tools": {
"register_manual": {
"limits": [
{
"counter": "register_manual_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}register_manual 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.
Registers a new tool provider by providing its call template. It is categorised as a Write tool in the UTCP-MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UTCP-MCP Bridge MCP server in PolicyLayer and add a rule for register_manual: 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 UTCP-MCP Bridge. Nothing to install.
register_manual 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 register_manual 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 register_manual. 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.
register_manual is provided by the UTCP-MCP Bridge MCP server (universal-tool-calling-protocol/utcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 UTCP-MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 UTCP-MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.