Detect vulnerable API endpoints in a project.
AI agents call detect_vulnerable_endpoints to retrieve information from Security-Use MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs security scanning and analysis to identify vulnerabilities, which is a read-only operation with no side effects on the scanned systems. It retrieves and reports vulnerability information but does not execute code, modify configurations, delete data, or commit financial transactions.
From the tool's definition Tool name 'detect_vulnerable_endpoints' and description 'Detect vulnerable API endpoints in a project' indicate scanning/detection activities without modifying systems. The verb 'detect' is observational.
Attacks that exploit this kind of access
Detect vulnerable API endpoints in a project. It is categorised as a Read tool in the Security-Use MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Security-Use MCP Server MCP server in PolicyLayer and add a rule for detect_vulnerable_endpoints: 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 Security-Use MCP Server. Nothing to install.
detect_vulnerable_endpoints 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 detect_vulnerable_endpoints 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 detect_vulnerable_endpoints. 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.
detect_vulnerable_endpoints is provided by the Security-Use MCP Server MCP server (security-use/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 →