install

Runs

SERVERTest SOURCEDave-London/Pare

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/io-github-dave-london-pare-test/install.md

WHAT IT DOES

What install does on Test

AI agents invoke install to trigger actions in Test. 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.

RISK

Why install is rated High

The tool is named 'install' and the description begins with 'Runs', strongly suggesting it executes an installation process (e.g., npm install, pip install). Installing packages executes external commands and modifies system state, which classifies as Execute. The blast radius is high because arbitrary package installation can introduce malicious code or alter system dependencies.

From the tool's definition Tool name 'install' on a server that 'Runs' (description truncated) in a context with package management tools like 'add-package', 'ansible-galaxy', 'bazel'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs install safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install, this is the rule to start with:

install Rate-limited

install stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install": {
      "limits": [
        {
          "counter": "install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every install call is checked against it from then on.

FAQ

Questions about install

What does the install tool do? +

Runs. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install? +

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

What risk level is install? +

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

Can I rate-limit install? +

Yes. Add a rate_limit block to the 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 install completely? +

Set action: deny in the PolicyLayer policy for 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 install? +

install is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Test, and thousands of servers like it.

This server

All 202 Test tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →