List engagements with optional filtering and pagination support
AI agents call list_engagements 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 queries and retrieves engagement records from DefectDojo with optional filters and pagination. It performs no create, update, delete, or execute operations. The filtering and pagination are read-only parameters that control which existing data is returned, not what data is modified. This is a standard data retrieval operation with minimal security risk.
From the tool's definition Tool name 'list_engagements' and description 'List engagements with optional filtering and pagination support' indicate a retrieval operation with no state modification.
Documented attack patterns abuse exactly the kind of access list_engagements 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 list_engagements:
{
"version": "1",
"default": "deny",
"tools": {
"list_engagements": {}
}
}list_engagements 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.
List engagements with optional filtering and pagination support. 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 list_engagements: 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.
list_engagements 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 list_engagements 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 list_engagements. 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.
list_engagements 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.