Emergency Contacts \u00b7 query emergencyContact. Variables: after, first, after1, first1, after2, filter, first2, order, after3, filter1, first3, order1, after4, filter2, first4, order2, id. Example variables: {\
AI agents call emergency_contact to retrieve information from ReliaQuest GreyMatter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves emergency contact information from the GreyMatter platform. It is a pure read operation that queries existing data without modifying, deleting, or executing any actions. The low severity reflects minimal risk even if an AI agent misuses it—it only exposes already-stored contact data.
From the tool's definition Tool name 'emergency_contact' with description 'query emergencyContact' indicates a data retrieval operation. The variables listed (after, first, filter, order, id) are pagination and filtering parameters typical of GraphQL queries.
Attacks that exploit this kind of access
Emergency Contacts \u00b7 query emergencyContact. Variables: after, first, after1, first1, after2, filter, first2, order, after3, filter1, first3, order1, after4, filter2, first4, order2, id. Example variables: {\. It is categorised as a Read tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for 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.
emergency_contact is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →