secrets
Secrets: filesystem scan, env variable audit, SSH key sprawl, git history leak detection
This record as markdown: /tools/defense/secrets.md
What secrets does on Defense
AI agents call secrets to retrieve information from Defense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | Root path to scan |
action | string | Yes | Secrets scanning action |
dryRun | boolean | — | Preview only |
repoPath | string | — | Path to git repository |
check_env | boolean | — | Check environment variables for sensitive names |
max_depth | number | — | Maximum directory depth to search |
scan_type | string | — | Type of secrets to scan for |
check_files | boolean | — | Check for exposed .env files on disk |
search_path | string | — | Root path to search for SSH keys |
check_authorized_keys | boolean | — | Also audit authorized_keys files |
Parameters from the server's own tool schema.
Why secrets is rated Low
The tool performs scanning and auditing operations — reading the filesystem, environment variables, SSH keys, and git history to detect leaks. These are read/query operations with no stated side effects. However, severity is medium because this tool accesses highly sensitive data (secrets, keys, credentials) and could expose critical information if misused or if results are logged/exfiltrated.
From the tool's definition filesystem scan, env variable audit, SSH key sprawl, git history leak detection
Risk signalsAccepts file system path (path) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs secrets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For secrets, this is the rule to start with:
secrets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Defense, apply this rule, and every secrets call is checked against it from then on.
Questions about secrets
Secrets: filesystem scan, env variable audit, SSH key sprawl, git history leak detection. It is categorised as a Read tool in the Defense MCP Server, which means it retrieves data without modifying state.
secrets accepts 10 parameters: path, action, dryRun, repoPath, check_env, max_depth, scan_type, check_files, search_path, check_authorized_keys. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for secrets: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Defense. Nothing to install.
secrets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the secrets rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for secrets. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
secrets is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
This server
Across the catalogue