update_call_order · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What update_call_order does on ReliaQuest GreyMatter MCP Server

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

WHY IT NEEDS A POLICY

Why update_call_order needs a policy

This tool modifies emergency contact configuration (call order) which is reversible—the order can be changed again. It affects operational response procedures but does not delete data, execute arbitrary code, or move money. Write category is appropriate; severity is medium because misconfiguration of emergency contacts could delay critical incident response, impacting response effectiveness.

From the tool's definition Tool name 'update_call_order' and description indicating a 'mutation' with parameters 'callOrder' and 'id' that modifies emergency contact call order. The GraphQL mutation pattern confirms data modification rather than retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_call_order Rate-limited

update_call_order 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": {
    "update_call_order": {
      "limits": [
        {
          "counter": "update_call_order_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 ReliaQuest GreyMatter MCP Server, so you can run agents against it safely.

FAQ

Questions about update_call_order

What does the update_call_order tool do? +

Emergency Contacts \u00b7 mutation updateCallOrder. Variables: callOrder, id. Example variables: {\. It is categorised as a Write tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_call_order? +

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

What risk level is update_call_order? +

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

Can I rate-limit update_call_order? +

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

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

update_call_order is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.