arch_record_component · Paparats MCP: Risk & Policy

WHAT IT DOES

What arch_record_component does on Paparats

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

WHY IT NEEDS A POLICY

Why arch_record_component needs a policy

The name implies writing/creating a new record (component) in the system. Without a description, confidence is lowered, but sibling tools like 'arch_record_decision' and 'arch_record_lesson' confirm a pattern of 'record_*' tools that write data. This is likely a Write operation that stores architectural component metadata.

From the tool's definition Tool name 'arch_record_component' suggests recording/creating an architectural component entry. No description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arch_record_component Rate-limited

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

FAQ

Questions about arch_record_component

What does the arch_record_component tool do? +

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

How do I enforce a policy on arch_record_component? +

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

What risk level is arch_record_component? +

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

Can I rate-limit arch_record_component? +

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

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

arch_record_component is provided by the Paparats MCP server (@paparats/cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.