AI agents use upload_plugin to create or update resources in Security Copilot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Security Copilot MCP Server environment.
The action of uploading implies creating or modifying plugin/skillset data in the Security Copilot system. This is reversible (plugins can be deleted or overwritten) and does not irreversibly destroy data or execute arbitrary code directly, so it falls into the Write category.
From the tool's definition Tool name is 'upload_plugin' which indicates creation or modification of plugins/skillsets in a security platform (Security Copilot). Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access upload_plugin gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Security Copilot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_plugin:
{
"version": "1",
"default": "deny",
"tools": {
"upload_plugin": {
"limits": [
{
"counter": "upload_plugin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_plugin 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.
Free to start. No card required.
upload_plugin. It is categorised as a Write tool in the Security Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Security Copilot MCP Server MCP server in PolicyLayer and add a rule for upload_plugin: 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 Security Copilot MCP Server. Nothing to install.
upload_plugin 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 upload_plugin 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 upload_plugin. 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.
upload_plugin is provided by the Security Copilot MCP Server MCP server (jguimera/securitycopilotmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Security Copilot MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Security Copilot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.