pulse_manage_tags · Pulse MCP: Risk & Policy

WHAT IT DOES

What pulse_manage_tags does on Pulse

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

WHY IT NEEDS A POLICY

Why pulse_manage_tags needs a policy

While the tool includes a delete operation, it applies only to tags (metadata), not to tasks themselves or critical data. Tag deletion is reversible through re-adding tags, making it Write rather than Destructive. The 'update' and 'list' operations reinforce the Write classification. This poses low blast radius risk - misuse would modify metadata rather than destroy irreplaceable task data.

From the tool's definition Tool description states 'Manage tags (list, update, delete)' - covers read operations (list), reversible modifications (update), and tag deletion. Tag management is a data modification operation without permanent destructive consequences to core tasks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pulse_manage_tags Rate-limited

pulse_manage_tags 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": {
    "pulse_manage_tags": {
      "limits": [
        {
          "counter": "pulse_manage_tags_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 Pulse, so you can run agents against it safely.

FAQ

Questions about pulse_manage_tags

What does the pulse_manage_tags tool do? +

Manage tags (list, update, delete). It is categorised as a Write tool in the Pulse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pulse_manage_tags? +

Register the Pulse MCP server in PolicyLayer and add a rule for pulse_manage_tags: 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 Pulse. Nothing to install.

What risk level is pulse_manage_tags? +

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

Can I rate-limit pulse_manage_tags? +

Yes. Add a rate_limit block to the pulse_manage_tags 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 pulse_manage_tags completely? +

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

pulse_manage_tags is provided by the Pulse MCP server (nemesiscodex/pulse-tm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.