rules_manager · Anchor MCP: Risk & Policy

WHAT IT DOES

What rules_manager does on Anchor

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

WHY IT NEEDS A POLICY

Why rules_manager needs a policy

This tool performs write operations on project rules, which are configuration data that persists across AI agent sessions. While not destructive (rules can be updated/reverted) and not immediately dangerous in isolation, misuse could allow an agent to alter project constraints, validation logic, or behavioral guidelines that other agents rely on.

From the tool's definition Tool can 'save/update rules' which modifies persistent project configuration state. Description explicitly states the capability to update/modify rules.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rules_manager Rate-limited

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

FAQ

Questions about rules_manager

What does the rules_manager tool do? +

Manage project rules: read current rules or save/update rules. It is categorised as a Write tool in the Anchor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rules_manager? +

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

What risk level is rules_manager? +

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

Can I rate-limit rules_manager? +

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

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

rules_manager is provided by the Anchor MCP server (thewillmoss/anchor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.