AI agents invoke security.test_idor to trigger actions in VulneraMCP. 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.
The tool name suggests it actively tests for IDOR vulnerabilities, meaning it sends crafted HTTP requests to target systems to probe access controls. This constitutes executing external operations against live targets. The description is empty, lowering confidence, but given the server context (automated vulnerability testing platform) and the 'test_' prefix, active exploitation/probing is the most likely behavior.
From the tool's definition Tool name 'security.test_idor' — 'test_idor' implies automated testing for Insecure Direct Object Reference vulnerabilities; part of a security testing platform integrating OWASP ZAP, Caido, Burp Suite
Documented attack patterns abuse exactly the kind of access security.test_idor gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VulneraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for security.test_idor:
{
"version": "1",
"default": "deny",
"tools": {
"security.test_idor": {
"limits": [
{
"counter": "security.test_idor_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}security.test_idor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
security.test_idor. It is categorised as a Execute tool in the VulneraMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vulnera MCP server in PolicyLayer and add a rule for security.test_idor: 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 VulneraMCP. Nothing to install.
security.test_idor 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 security.test_idor 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 security.test_idor. 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.
security.test_idor is provided by the Vulnera MCP server (telmon95/vulneramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 VulneraMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 VulneraMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.