Skip to main content
Glama
step-security

stepsecurity-mcp

Official

delete_suppression_rule

Delete a suppression rule to prevent new detections from being suppressed by it. Existing suppressed detections are not unsuppressed; they retain the deleted rule ID.

Instructions

Delete a suppression rule. WRITE OPERATION — requires confirm: true. NOTE: deleting a rule does NOT un-suppress detections it previously matched; they remain in the suppressed state with the deleted rule_id attached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerNoStepSecurity customer/tenant identifier. Optional — falls back to STEP_SECURITY_CUSTOMER env var.
ruleIdYesRule id to delete
confirmYesSet to true to actually execute the write. Any other value (including omitted) returns an error — this is a safety check so the LLM cannot write without explicit user approval.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses critical behavioral traits: it's a write operation, requires confirmation, and importantly notes that deletion does not reverse prior suppressions. This goes beyond the schema and addresses a key side effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences. First sentence states the core purpose; second sentence adds a critical behavioral note. No fluff, front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the key behavioral aspect of deletion. Missing is what the return value or success response looks like, but for a delete operation, it is sufficient. The schema fully documents parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds little beyond what is already in the schema. It mentions the confirm requirement but doesn't elaborate on parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'Delete' and the resource 'suppression rule', distinguishing it from sibling tools like create, update, list, and preview. The purpose is unambiguous and specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit instructions on when to use this tool versus alternatives. Implicit from the name, but lacks guidance on prerequisites or timing. The behavioral note about not unsuppressing is useful for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/step-security/stepsecurity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server