delete_api_key_by_id

API Keys \u00b7 mutation deleteApiKeyById. Variables: id, user. Example variables: {\

Server ReliaQuest GreyMatter MCP Server space-c0wboy/reliaquest-greymatter-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_api_key_by_id does on ReliaQuest GreyMatter MCP Server

AI agents call delete_api_key_by_id to permanently remove resources in ReliaQuest GreyMatter MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_api_key_by_id needs a policy

Deleting an API key is an irreversible action that cannot be undone without recreating the key. This is destructive because: (1) it permanently removes authentication credentials, (2) any integrations or applications using that key will immediately stop functioning, (3) there is no undo capability inherent to the operation.

From the tool's definition Tool name 'delete_api_key_by_id' explicitly indicates deletion of an API key resource via mutation operation. The description confirms this is a mutation operation (deleteApiKeyById) that removes an API key identified by id.

Questions about delete_api_key_by_id

What does the delete_api_key_by_id tool do? +

API Keys \u00b7 mutation deleteApiKeyById. Variables: id, user. Example variables: {\. It is categorised as a Destructive tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_api_key_by_id? +

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

delete_api_key_by_id is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_api_key_by_id? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.