Return a list of hands-on SecDim secure coding labs related to a detected or suspected vulnerability. Use this tool to: - Find secure coding learning labs for specific vulnerabilities like XSS, SQL Injection, etc. - Explore OWASP Top 10 vulnerabilities and related labs - Pro...
Part of the SecDim Secure Coding Labs MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_vulnerable_practice_labs to retrieve information from SecDim Secure Coding Labs without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_vulnerable_practice_labs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_vulnerable_practice_labs:
rules:
- action: allowSee the full SecDim Secure Coding Labs policy for all 2 tools.
Agents calling read-class tools like get_vulnerable_practice_labs have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Return a list of hands-on SecDim secure coding labs related to a detected or suspected vulnerability. Use this tool to: - Find secure coding learning labs for specific vulnerabilities like XSS, SQL Injection, etc. - Explore OWASP Top 10 vulnerabilities and related labs - Provide additional resources and guides to help developers improve their secure coding skills Args: search: Search term for the vulnerability (e.g., 'xss', 'sql-injection', 'injection') cwe: Common Weakness Enumeration (CWE) ID to filter by owasp: OWASP category to filter by (e.g., 'a03:2021') technology: Technology or framework to filter by (e.g., 'react', 'django') language: Programming language to filter by (e.g., 'javascript', 'python') Labs are secure coding challenges each simulating a real vulnerability. They are tagged with the following difficulty levels - Trivial: Easy to find and path vulnerabilities. It can be completed in 5-10 minutes. 1-15 points. - Easy: Known vulnerabilities. It can be completed in 10-30 minutes. 16-35 points. - Medium: Known vulnerabilities but require defence-in-depth patch. It can be completed in 20-30 minutes. 36-70 points. - Hard: Hard to find or patch vulnerabilities. It can be completed in 30-60 minutes. 71-100 points. - Battle: SecDim Flagship attack and defence challenge that require both vulnerability exploitation and mitigation skills. Points are accumulated. Returns: Dictionary containing labs results or error If there are no results, user can perform a manual search on https://play.secdim.com/browse . It is categorised as a Read tool in the SecDim Secure Coding Labs MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_vulnerable_practice_labs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SecDim Secure Coding Labs MCP server.
get_vulnerable_practice_labs 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 get_vulnerable_practice_labs rule in your Intercept 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 Intercept policy for get_vulnerable_practice_labs. 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.
get_vulnerable_practice_labs is provided by the SecDim Secure Coding Labs MCP server (pi3ch/secdim). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept