delete_pod

Access Groups \u00b7 mutation deletePod. Variables: id. Example variables: {\

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

What delete_pod does on ReliaQuest GreyMatter MCP Server

AI agents call delete_pod 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_pod needs a policy

The tool performs an irreversible deletion operation on a pod (likely a container or orchestration unit in the GreyMatter platform). Deletion operations that cannot be undone fall into the Destructive category. The severity is high because deleting infrastructure components could cause service disruption or data loss, though the impact depends on what the pod controls.

From the tool's definition Tool name is 'delete_pod' and description indicates it is a 'mutation deletePod' - both the imperative verb 'delete' and the GraphQL mutation designation explicitly indicate irreversible deletion of a pod resource.

Questions about delete_pod

What does the delete_pod tool do? +

Access Groups \u00b7 mutation deletePod. Variables: id. 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_pod? +

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

delete_pod 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_pod? +

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

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

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