update_features · Pulse Workflow MCP Server MCP

WHAT IT DOES

What update_features does on Pulse Workflow MCP Server

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

WHY IT NEEDS A POLICY

Why update_features needs a policy

This tool modifies workflow features in a reversible manner (typical CRUD update operation). It does not delete data (Destructive), execute external commands (Execute), move money (Financial), or merely read (Read). The 'partial' descriptor suggests targeted updates rather than wholesale replacement, typical of Write operations.

From the tool's definition Tool name 'update_features' with description 'Update features (partial)' indicates modification of existing workflow feature configurations. Part of a workflow management server that enables 'create, edit, and publish' operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_features Rate-limited

update_features 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_features": {
      "limits": [
        {
          "counter": "update_features_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 Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about update_features

What does the update_features tool do? +

Update features (partial). It is categorised as a Write tool in the Pulse Workflow 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_features? +

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

What risk level is update_features? +

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

Can I rate-limit update_features? +

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

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

update_features is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.