Skip to main content
Glama
Sign In
stepsecurity-mcp

stepsecurity-mcp

Official
by step-security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_suppression_rules

Retrieve all configured suppression rules for your tenant to check for duplicates or near-overlaps before creating a new rule, ensuring efficient detection rule management.

Instructions

List all suppression (detection) rules configured for the tenant. Use this before creating a new rule to check for duplicates or near-overlaps. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_suppression_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerNoStepSecurity customer/tenant identifier. Optional — falls back to STEP_SECURITY_CUSTOMER env var.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The description labels the tool as 'Read-only,' which is important but minimal. No annotations exist, so the description carries full burden; additional behavioral traits like rate limits or authentication needs are not disclosed.

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?

Three sentences, front-loaded with key information, no unnecessary words. Every sentence adds value.

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?

Given a simple list tool with no output schema, the description covers purpose, usage, and read-only nature. Could mention response format, but not essential.

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 description coverage is 100% for the single optional parameter, and the description does not add further semantic value beyond the schema. Baseline score of 3 is appropriate.

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?

Description clearly states the verb 'list' and resource 'suppression (detection) rules' with tenant scope. This distinguishes it from sibling tools like create_suppression_rule or delete_suppression_rule.

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

Usage Guidelines4/5

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

Explicitly advises using the tool before creating a new rule to check for duplicates or near-overlaps, providing clear context. However, it does not mention when not to use or suggest alternatives.

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