update_profile · Cobalt Strike MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_profile does on Cobalt Strike MCP Server

AI agents use update_profile to create or update resources in Cobalt Strike MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cobalt Strike MCP Server environment.

WHY IT NEEDS A POLICY

Why update_profile needs a policy

This tool modifies (writes) configuration settings that control red team operations, but does not irreversibly delete data (not Destructive), execute arbitrary commands on targets (not Execute), or move money (not Financial).

From the tool's definition Tool name 'update_profile' and description 'Update Malleable C2 profile' indicate modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_profile Rate-limited

update_profile 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_profile": {
      "limits": [
        {
          "counter": "update_profile_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about update_profile

What does the update_profile tool do? +

Update Malleable C2 profile. It is categorised as a Write tool in the Cobalt Strike MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_profile? +

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

What risk level is update_profile? +

update_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_profile? +

Yes. Add a rate_limit block to the update_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.

How do I block update_profile completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_profile? +

update_profile is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.