New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mcp_install

Install a new MCP server. Use package+command+args for direct package installation (e.g., npm packages), or just name for registry-based installation

SERVER1MCP Server SOURCE1mcp-app/agent
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1mcp-app-agent/mcp-install.md

What mcp_install does on 1MCP Server

AI agents invoke mcp_install to trigger actions in 1MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why mcp_install is rated High

Installing a package executes installation scripts and potentially arbitrary code from the package, and adds a new MCP server to the aggregation layer. This goes beyond a simple write operation as it triggers execution of package manager commands and install scripts, potentially altering system state significantly.

From the tool's definition "Install a new MCP server" and "direct package installation (e.g., npm packages)"

Questions about mcp_install

What does the mcp_install tool do? +

Install a new MCP server. Use package+command+args for direct package installation (e.g., npm packages), or just name for registry-based installation. It is categorised as a Execute tool in the 1MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mcp_install? +

Register the 1MCP Server MCP server in PolicyLayer and add a rule for mcp_install: 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 1MCP Server. Nothing to install.

What risk level is mcp_install? +

mcp_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mcp_install? +

Yes. Add a rate_limit block to the mcp_install 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.

How do I block mcp_install completely? +

Set action: deny in the PolicyLayer policy for mcp_install. 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.

What MCP server provides mcp_install? +

mcp_install is provided by the 1MCP Server MCP server (1mcp-app/agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 1MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 1MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.