CORS misconfiguration scanner
AI agents invoke corscanner to trigger actions in PenTest MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
CORScanner actively probes remote targets by sending crafted HTTP requests to detect CORS misconfigurations. This is an external operation whose effects depend on arguments (target URL/domain). On a pentest server context, misuse could mean scanning unauthorized targets, constituting unauthorized access attempts. Severity is high given the offensive security context and potential for abuse against external systems.
From the tool's definition CORS misconfiguration scanner — runs an active scanning tool against a target to detect CORS misconfigurations, part of a penetration testing server with 30+ security tools
Attacks that exploit this kind of access
CORS misconfiguration scanner. It is categorised as a Execute tool in the PenTest MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PenTest MCP Server MCP server in PolicyLayer and add a rule for corscanner: 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 PenTest MCP Server. Nothing to install.
corscanner is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the corscanner 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 corscanner. 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.
corscanner is provided by the PenTest MCP Server MCP server (mohitsahoo/mcptoolforwebvulnerabilities-). 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 →