web_add_package
AI agents use web_add_package to create or update resources in PC-Control MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PC-Control MCP Server environment.
Adding a package modifies system dependencies and installed software, which is a reversible write operation. However, it could have significant side effects (installing malicious packages, breaking compatibility, consuming resources), warranting 'high' severity. Confidence is moderate-to-good due to empty description but clear naming convention context.
From the tool's definition Tool name 'web_add_package' combined with server context showing package management capabilities ('web_detect_package_manager' is a sibling tool). The description is empty, but the name strongly indicates package installation/addition.
Attacks that exploit this kind of access
web_add_package. It is categorised as a Write tool in the PC-Control MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PC-Control MCP Server MCP server in PolicyLayer and add a rule for web_add_package: 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 PC-Control MCP Server. Nothing to install.
web_add_package 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 web_add_package 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 web_add_package. 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.
web_add_package is provided by the PC-Control MCP Server MCP server (krsnmlna1/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 →