project_add_package
A write tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/project-add-package.md
What project_add_package does on Mcp Anything
AI agents use project_add_package to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.
Why project_add_package is rated Medium
Adding a package to a project modifies the project state (likely package.json, requirements.txt, or similar manifest) reversibly. This is a Write operation rather than Destructive (can be undone by removing the package) or Execute (no arbitrary code execution, just dependency declaration). Medium severity because a rogue agent could add malicious or incompatible dependencies, but the impact is generally recoverable.
From the tool's definition Tool name 'project_add_package' indicates creation/modification of project dependencies. The 'add' verb suggests a write operation that creates or modifies project configuration reversibly.
Attacks that exploit this kind of access
The rule that runs project_add_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_add_package, this is the rule to start with:
project_add_package 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 Mcp Anything, apply this rule, and every project_add_package call is checked against it from then on.
Questions about project_add_package
project_add_package is a write tool on the Mcp Anything MCP server. It is categorised as a Write tool in the Mcp Anything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for project_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 Mcp Anything. Nothing to install.
project_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 project_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 project_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.
project_add_package is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue