Skip to main content
Glama
Sign In
mcp-security-scanner

mcp-security-scanner

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rt_pin_tools

Creates a cryptographic hash of MCP server tool definitions and stores it as a pin file to detect unauthorized changes later.

Instructions

Connect to server, SHA-256 hash every tool definition (name + description + schema), store as a pin file. Use rt_verify_pins later to detect tool definition changes (rug pull detection).

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": {
      "pin_name": "<pin_name>"
    },
    "name": "rt_pin_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoAdditional environment variables for stdio
urlNoMCP server URL for HTTP/SSE transport (e.g. 'http://localhost:3000/mcp')
argsNoCommand arguments for stdio (e.g. ['run', 'server.js'])
commandNoServer command for stdio transport (e.g. 'node', 'bun', 'npx')
headersNoCustom HTTP headers (e.g. { 'Authorization': 'Bearer token' })
pin_nameYesName for this pin (used as filename, e.g. 'my-mcp-server')
timeout_msNoConnection timeout in milliseconds (default: 30000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • changedInput schema / properties / args / description
      Previous value: -"Command arguments (e.g. ['run', 'server.js'])"New value: +"Command arguments for stdio (e.g. ['run', 'server.js'])"
    • changedInput schema / properties / command / description
      Previous value: -"Server command to execute (e.g. 'node', 'bun', 'npx')"New value: +"Server command for stdio transport (e.g. 'node', 'bun', 'npx')"
    • changedInput schema / properties / env / description
      Previous value: -"Additional environment variables"New value: +"Additional environment variables for stdio"
    • addedInput schema / properties / headers
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Custom HTTP headers (e.g. { 'Authorization': 'Bearer token' })",
+  "type": "object"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "MCP server URL for HTTP/SSE transport (e.g. 'http://localhost:3000/mcp')",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "command",
-  "pin_name"
-]New value: +[
+  "pin_name"
+]
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The description discloses key behaviors: connects to server, hashes tool definitions, stores pin file. However, without annotations, it lacks details like side effects (e.g., overwriting existing pins), storage location, or error handling. Adequate but could be more transparent.

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 sentences, front-loaded with the action, followed by usage context. No unnecessary words. Highly concise and well-structured.

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?

Given the complexity (7 params, nested objects) and lack of output schema/annotations, the description covers the main purpose but omits details like return values, idempotency, and error scenarios. It is moderately complete.

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 all parameters are described in the schema. The description adds little beyond the schema, except context that pin_name is used as a filename. Baseline 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?

The description clearly states the tool's function: connecting to a server, hashing tool definitions, and storing as a pin file. It explicitly mentions the purpose ('rug pull detection') and distinguishes it from sibling tools like rt_verify_pins.

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?

The description provides clear usage context: use this tool to create a baseline pin file, then later use rt_verify_pins for change detection. It implies a workflow but does not explicitly state when not to use or provide 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