AI agents invoke mitre_campaign_profile to trigger actions in Mitre. 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.
mitre_campaign_profile triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Build a technique profile from observed techniques for campaign analysis and attribution. It is categorised as a Execute tool in the Mitre MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mitre MCP server in PolicyLayer and add a rule for mitre_campaign_profile: 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 Mitre. Nothing to install.
mitre_campaign_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mitre_campaign_profile 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 mitre_campaign_profile. 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.
mitre_campaign_profile is provided by the Mitre MCP server (solomonneas/mitre-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.