Skip to main content
Glama

Security scan for skills and agent config

secure_scan
Read-only

Scan a folder for risky agent setup—secrets and pipe-to-shell skills, unpinned or remote MCP servers, broad permissions, risky dependencies—and return severity-ranked fixes. Read-only.

Instructions

Scan a folder for risky agent setup: secrets and pipe-to-shell in skills, unpinned or remote-package MCP servers in .mcp.json, broad permissions in .claude/settings.json, risky dependencies in skill scripts. Returns findings by severity with a fix for each. 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": "secure_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoThe folder to scan. Relative paths resolve from the folder the server was started in. Default "."

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with those safety properties. Beyond the annotations, it adds useful behavioral detail by listing the exact risk categories examined and stating that findings are returned by severity with a fix for each.

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 compact and front-loaded: it first states the action and scope, then enumerates what is checked, then summarizes the return, and ends with the read-only constraint. Every sentence contributes useful information without filler.

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 one-parameter read-only scanner with no output schema, the description provides enough context to invoke it correctly: it identifies the folder to scan through the schema, lists the risk categories, and summarizes the returned findings. It does not detail the exact finding structure or severity values, which keeps it from being fully 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?

There is only one parameter and the schema description coverage is 100%, so the schema already explains that path is the folder to scan, how relative paths resolve, and the default. The description mentions scanning a folder but does not add syntax or format details beyond the schema, making the baseline score 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 states a specific verb and resource: scan a folder for risky agent setup, with concrete checks such as secrets, pipe-to-shell, MCP servers, settings permissions, and dependencies. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like check_agents or review_skill.

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?

The security-review context is implied by the enumerated risky patterns and files, so an agent can infer this is for auditing agent configuration. However, there is no explicit guidance on when to use this versus check_agents, review_skill, or other siblings, and no when-not-to-use conditions.

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