libi.register_mcp_server
Register a new external MCP server so it becomes available in future agent sessions. Use this when the user asks you to add an MCP tool. Install any required npm packages first (e.g., via npx), then call this tool to wire up the server config. The server will be available after the next session s...
This record as markdown: /tools/libi/libi.register-mcp-server.md
What libi.register_mcp_server does on Libi
AI agents use libi.register_mcp_server to create or update resources in Libi, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Libi environment.
Why libi.register_mcp_server is rated Medium
Creates persistent MCP server configuration enabling new tool access; reversible but grants significant capability expansion.
From the tool's definition Register a new external MCP server, wire up the server config, becomes available in future agent sessions.
Attacks that exploit this kind of access
The rule that runs libi.register_mcp_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.register_mcp_server, this is the rule to start with:
libi.register_mcp_server 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Libi, apply this rule, and every libi.register_mcp_server call is checked against it from then on.
Questions about libi.register_mcp_server
Register a new external MCP server so it becomes available in future agent sessions. Use this when the user asks you to add an MCP tool. Install any required npm packages first (e.g., via npx), then call this tool to wire up the server config. The server will be available after the next session starts. Ask the user whether the server should require approval before use. It is categorised as a Write tool in the Libi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Libi MCP server in PolicyLayer and add a rule for libi.register_mcp_server: 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 Libi. Nothing to install.
libi.register_mcp_server 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 libi.register_mcp_server 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 libi.register_mcp_server. 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.
libi.register_mcp_server is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Libi, and thousands of servers like it.
This server
Across the catalogue