update_emergency_contact

WHAT IT DOES

What update_emergency_contact does on ReliaQuest GreyMatter MCP Server

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

This tool modifies emergency contact data, which is a reversible write operation. While contact information is sensitive, the action itself is not destructive (data can be updated again), not financial, and not code execution.

From the tool's definition Tool name 'update_emergency_contact' and description indicating it is a 'mutation updateEmergencyContact' for emergency contacts. The mutation operation confirms this is a write/update action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_emergency_contact Rate-limited

update_emergency_contact 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_emergency_contact": {
      "limits": [
        {
          "counter": "update_emergency_contact_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_emergency_contact

What does the update_emergency_contact tool do? +

Emergency Contacts \u00b7 mutation updateEmergencyContact. Variables: input. 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_emergency_contact? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for update_emergency_contact: 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_emergency_contact? +

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

Can I rate-limit update_emergency_contact? +

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

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

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