AI agents call get_engagement to retrieve information from DefectDojo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data about a specific engagement without side effects. It is a read-only query operation that does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an agent could only discover information already stored in DefectDojo, not alter the system or cause harm.
From the tool's definition Tool name is 'get_engagement' and description states 'Get a specific engagement by ID' — a straightforward retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_engagement gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DefectDojo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_engagement:
{
"version": "1",
"default": "deny",
"tools": {
"get_engagement": {}
}
}get_engagement is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific engagement by ID. It is categorised as a Read tool in the DefectDojo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DefectDojo MCP Server MCP server in PolicyLayer and add a rule for get_engagement: 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 DefectDojo MCP Server. Nothing to install.
get_engagement 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_engagement 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 get_engagement. 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_engagement is provided by the DefectDojo MCP Server MCP server (jamiesonio/defectdojo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DefectDojo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 DefectDojo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.