Register a remote MCP server URL so obot proxies it. Use for HTTP/SSE MCPs hosted elsewhere.
AI agents use add_remote_mcp to create or update resources in Obot Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obot Admin environment.
This tool creates a new remote MCP server registration in the obot gateway, modifying the system's configuration state. It is reversible (can be deleted via delete_mcp_server sibling tool), so it qualifies as Write rather than Destructive.
From the tool's definition Tool description states 'Register a remote MCP server URL' and 'obot proxies it', indicating creation/addition of a new configuration entry in the gateway's registry. The name 'add_' prefix and verb 'register' confirm write semantics.
Attacks that exploit this kind of access
Register a remote MCP server URL so obot proxies it. Use for HTTP/SSE MCPs hosted elsewhere. It is categorised as a Write tool in the Obot Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obot Admin MCP server in PolicyLayer and add a rule for add_remote_mcp: 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 Obot Admin. Nothing to install.
add_remote_mcp 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 add_remote_mcp 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 add_remote_mcp. 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.
add_remote_mcp is provided by the Obot Admin MCP server (kiarashedraki/obot-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →