Scan the codebase for potential secret leaks. Detects AWS keys, GitHub tokens, Stripe keys, private keys, and more.
AI agents call keyway_scan to retrieve information from Keyway MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes data from the codebase to identify potential secrets—a read-only operation. It produces informational output about existing leaks but does not create, modify, execute, or delete resources. The risk is low because misuse would only expose what secrets exist in the codebase (information already there), not cause destructive or financial harm or execute arbitrary code.
From the tool's definition Tool description states it "Scan[s] the codebase for potential secret leaks" and "Detects AWS keys, GitHub tokens, Stripe keys, private keys, and more." The verb "scan" and "detect" indicate passive analysis and querying of the codebase without modifying,…
Attacks that exploit this kind of access
Scan the codebase for potential secret leaks. Detects AWS keys, GitHub tokens, Stripe keys, private keys, and more. It is categorised as a Read tool in the Keyway MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Keyway MCP Server MCP server in PolicyLayer and add a rule for keyway_scan: 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 Keyway MCP Server. Nothing to install.
keyway_scan 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 keyway_scan 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 keyway_scan. 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.
keyway_scan is provided by the Keyway MCP Server MCP server (keywaysh/keyway-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →