Security check — scan a directory for exposed API tokens and hardcoded secrets only. Returns pass/fail with a list of any exposed credentials found. Use this before committing code or in CI pipelines.
AI agents call check_secrets to retrieve information from Ai Scanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a security audit by reading directory contents and analyzing them for patterns matching API tokens and secrets. It has no side effects—it does not create, modify, delete, execute code, or trigger external operations. The returned information is passive reporting.
From the tool's definition Tool description states it 'scan[s] a directory for exposed API tokens and hardcoded secrets' and 'Returns pass/fail with a list of any exposed credentials found.' The verb 'scan' and 'returns' indicate data retrieval and analysis with no modification or…
Attacks that exploit this kind of access
Security check — scan a directory for exposed API tokens and hardcoded secrets only. Returns pass/fail with a list of any exposed credentials found. Use this before committing code or in CI pipelines. It is categorised as a Read tool in the Ai Scanner MCP Server, which means it retrieves data without modifying state.
Register the Ai Scanner MCP server in PolicyLayer and add a rule for check_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 Ai Scanner. Nothing to install.
check_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 check_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 check_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.
check_secrets is provided by the Ai Scanner MCP server (sky-in-code/ai-scanner-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 →