delete_reference_list_column

Reference Lists \u00b7 mutation deleteReferenceListColumn. 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_reference_list_column does on ReliaQuest GreyMatter MCP Server

AI agents call delete_reference_list_column 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_reference_list_column needs a policy

The tool's primary function is to permanently delete data (a column from a reference list) without the ability to undo the operation. This matches the 'Destructive' category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius depends on which reference list column is targeted, any deletion of structured data in an incident response/case management platform…

From the tool's definition Tool name 'delete_reference_list_column' explicitly uses the verb 'delete' and performs a mutation operation that removes a column from a reference list. The GraphQL mutation pattern confirms this is an irreversible deletion action.

Questions about delete_reference_list_column

What does the delete_reference_list_column tool do? +

Reference Lists \u00b7 mutation deleteReferenceListColumn. 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_reference_list_column? +

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

delete_reference_list_column 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_reference_list_column? +

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

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

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