Skip to main content
Glama
Sign In
stepsecurity-mcp

stepsecurity-mcp

Official
by step-security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_suppression_rule

Retrieve a specific suppression rule by its unique ID to view its configuration. Use this tool to investigate security rule suppressions in the StepSecurity platform.

Instructions

Get one suppression rule by id. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ruleId": "<ruleId>"
    },
    "name": "get_suppression_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerNoStepSecurity customer/tenant identifier. Optional — falls back to STEP_SECURITY_CUSTOMER env var.
ruleIdYesRule id (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

The description says 'Read-only,' which hints at safety, but with no annotations, more detail would be beneficial. It does not disclose error handling, authentication needs, or what happens if the rule does not exist.

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?

The description is extremely concise at only two short sentences. Every word adds value, no fluff. It is front-loaded and efficient.

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

Completeness3/5

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

For a simple get-by-ID tool with no output schema and full schema coverage, the description is minimally adequate. It explains the operation and read-only nature but omits return value context and error scenarios.

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?

The input schema already provides full descriptions for both parameters (100% coverage). The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states it retrieves a single suppression rule by ID and indicates it is read-only. However, it does not differentiate from sibling tools like list_suppression_rules or preview_suppression_rule, which could cause confusion for an AI agent.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as list_suppression_rules or preview_suppression_rule. An agent might not know this is appropriate only when a specific rule ID is known.

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

Deploy Server

Other Tools