scan_project_security
Perform comprehensive security vulnerability scan of a project
This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/scan-project-security.md
What scan_project_security does on Claude MCP Server Ecosystem
AI agents call scan_project_security to retrieve information from Claude MCP Server Ecosystem 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_security is rated Low
Security scanning reads and analyzes project files/code to identify vulnerabilities without modifying anything. It's a read/analysis operation with no side effects. Medium severity because it may access sensitive source code, configurations, and secrets across a project, and scan results themselves could be sensitive if exposed to a malicious actor.
From the tool's definition 'scan_project_security' and 'Perform comprehensive security vulnerability scan of a project'
Attacks that exploit this kind of access
The rule that runs scan_project_security safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP Server Ecosystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_project_security, this is the rule to start with:
scan_project_security 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 Claude MCP Server Ecosystem, apply this rule, and every scan_project_security call is checked against it from then on.
Questions about scan_project_security
Perform comprehensive security vulnerability scan of a project. It is categorised as a Read tool in the Claude MCP Server Ecosystem MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Ecosystem MCP server in PolicyLayer and add a rule for scan_project_security: 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 Claude MCP Server Ecosystem. Nothing to install.
scan_project_security 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_security 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_security. 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_security is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP Server Ecosystem, and thousands of servers like it.
This server
Across the catalogue