scan_project_secrets
Scan a workspace-relative path for likely hardcoded credentials without exposing values
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/scan-project-secrets.md
What scan_project_secrets does on Project Guardian MCP
AI agents call scan_project_secrets to retrieve information from Project Guardian MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_project_secrets is rated Low
This is a security scanning tool that performs read-only inspection of project files to identify potential credential patterns. It retrieves or queries information about likely secrets without retrieving or exfiltrating actual secret values. This is a Read category tool - it has no side effects, creates no data modifications, and performs detection/analysis only.
From the tool's definition Tool is named 'scan_project_secrets' and described as 'Scan a workspace-relative path for likely hardcoded credentials without exposing values'. The verb 'scan' indicates data retrieval/inspection only.
Attacks that exploit this kind of access
The rule that runs scan_project_secrets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_project_secrets, this is the rule to start with:
scan_project_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 Project Guardian MCP, apply this rule, and every scan_project_secrets call is checked against it from then on.
Questions about scan_project_secrets
Scan a workspace-relative path for likely hardcoded credentials without exposing values. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.
Register the Project Guardian MCP server in PolicyLayer and add a rule for scan_project_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 Project Guardian MCP. Nothing to install.
scan_project_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 scan_project_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 scan_project_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.
scan_project_secrets is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue