update_feature · Follow Plan MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_feature does on Follow Plan MCP Server

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

WHY IT NEEDS A POLICY

Why update_feature needs a policy

The tool modifies feature records within a project management system with SQLite persistence. While reversible (features can be updated again), it changes application state and could impact project planning if misused by an AI agent (e.g., corrupting feature specifications, changing requirements). This is Write-level risk: creates or modifies data reversibly.

From the tool's definition Tool name 'update_feature' and description 'Update an existing feature' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_feature Rate-limited

update_feature 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_feature": {
      "limits": [
        {
          "counter": "update_feature_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 Follow Plan MCP Server, so you can run agents against it safely.

FAQ

Questions about update_feature

What does the update_feature tool do? +

Update an existing feature. It is categorised as a Write tool in the Follow Plan 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_feature? +

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

What risk level is update_feature? +

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

Can I rate-limit update_feature? +

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

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

update_feature is provided by the Follow Plan MCP Server MCP server (vibeclasses/follow-plan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

update_feature is one line of Follow Plan MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →