Skip to main content
Glama
mcp-security-auditor

mcp-security-auditor

by jashory

list_security_rules

Lists all 13 CWE-mapped static security rules implemented by the auditor, helping users identify which checks are available for detecting issues before deployment.

Instructions

List all 13 CWE-mapped static security rules implemented by mcp-agent-security-auditor.

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_security_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only catalog operation and the count of 13 rules is helpful scope information, but the description does not explicitly state there are no side effects, whether results are static or configurable, or what the returned rule entries contain.

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?

A single sentence with no filler. The core fact (a list of 13 CWE-mapped security rules) is front-loaded and every clause adds information.

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?

For a zero-parameter, read-only listing tool with no output schema and no annotations, the description covers what is listed and how many entries exist. It could optionally hint at what each rule entry includes (rule ID, CWE mapping, description), but nothing essential for calling it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate at the parameter level. The baseline of 4 applies, and the description appropriately spends its words on what is returned rather than on nonexistent inputs.

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 states a specific verb (list) and resource (static security rules), and adds useful qualifiers: 13 rules, CWE-mapped, implemented by mcp-agent-security-auditor. It does not explicitly distinguish itself from scan_path or remediate_path, so an agent must infer that this is the catalog-lookup tool rather than an execution tool.

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?

There is no explicit when-to-use guidance and no mention of the sibling tools. The catalog nature of the tool implies its purpose, but nothing tells the agent when to call this instead of scan_path or remediate_path, nor whether it should be called before scanning.

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