register_production_test · Fichapao MCP: Risk & Policy

WHAT IT DOES

What register_production_test does on Fichapao

AI agents use register_production_test 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 register_production_test needs a policy

This tool creates a new production test record associated with a recipe version. It modifies the database state by adding data (a test registration), which is reversible—test records can be deleted or corrected. It does not execute arbitrary production operations, delete data irreversibly, or move money.

From the tool's definition Tool name 'register_production_test' and description 'Registra um teste de producao para uma versao da ficha' (Registers a production test for a recipe version) indicates creation/recording of test data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_production_test Rate-limited

register_production_test 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": {
    "register_production_test": {
      "limits": [
        {
          "counter": "register_production_test_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 register_production_test

What does the register_production_test tool do? +

Registra um teste de producao para uma versao da ficha. 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 register_production_test? +

Register the Fichapao MCP server in PolicyLayer and add a rule for register_production_test: 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 register_production_test? +

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

Can I rate-limit register_production_test? +

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

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

register_production_test 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.