approve_version · Fichapao MCP: Risk & Policy

WHAT IT DOES

What approve_version does on Fichapao

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

WHY IT NEEDS A POLICY

Why approve_version needs a policy

approve_version modifies existing recipe version records by changing their approval status and potentially promoting version numbers. This is a Write operation rather than Execute because it updates structured data with deterministic effects (approval state transition), not arbitrary code execution. It's not Destructive because the change is reversible and doesn't delete data.

From the tool's definition Tool description states 'Aprova uma versao' (approves a version) and 'Versoes 0.x viram 1.0' (versions 0.x become 1.0), indicating state modification of recipe versions in the database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

approve_version Rate-limited

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

FAQ

Questions about approve_version

What does the approve_version tool do? +

Aprova uma versao se nao houver pendencias criticas. Versoes 0.x viram 1.0 na primeira aprovacao. It is categorised as a Write tool in the Fichapao MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on approve_version? +

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

What risk level is approve_version? +

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

Can I rate-limit approve_version? +

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

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

approve_version is provided by the Fichapao MCP server (kratos4ai/fichapao-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.