pruva_update_feature · Pruva MCP: Risk & Policy

WHAT IT DOES

What pruva_update_feature does on Pruva

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

WHY IT NEEDS A POLICY

Why pruva_update_feature needs a policy

This tool modifies feature data within the Pruva product management system. It is categorized as Write rather than Execute because it performs a standard data modification operation (update) without executing arbitrary code or triggering complex side effects.

From the tool's definition Tool name 'pruva_update_feature' and description 'Update a feature' indicate modification of existing data. The verb 'update' is characteristic of Write operations that create or modify data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pruva_update_feature Rate-limited

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

FAQ

Questions about pruva_update_feature

What does the pruva_update_feature tool do? +

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

How do I enforce a policy on pruva_update_feature? +

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

What risk level is pruva_update_feature? +

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

Can I rate-limit pruva_update_feature? +

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

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

pruva_update_feature is provided by the Pruva MCP server (pruva-ai/pruva-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.