record_routing_preference · Metis Public Health MCP

WHAT IT DOES

What record_routing_preference does on Metis Public Health

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

WHY IT NEEDS A POLICY

Why record_routing_preference needs a policy

The name 'record_routing_preference' strongly implies writing/persisting a user preference about how requests are routed to the 34 specialist agents. This is likely a Write operation (storing a configuration preference). The empty description lowers confidence. Severity is medium because misconfigured routing preferences could misdirect queries to wrong agents, but it is likely reversible.

From the tool's definition Tool name: record_routing_preference — description is empty/uninformative

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_routing_preference Rate-limited

record_routing_preference 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": {
    "record_routing_preference": {
      "limits": [
        {
          "counter": "record_routing_preference_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 Metis Public Health, so you can run agents against it safely.

FAQ

Questions about record_routing_preference

What does the record_routing_preference tool do? +

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

How do I enforce a policy on record_routing_preference? +

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

What risk level is record_routing_preference? +

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

Can I rate-limit record_routing_preference? +

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

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

record_routing_preference is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.