Query compliance mapping for an engagement's findings. Frameworks: pci_dss, hipaa, soc2, owasp, all Returns findings grouped by compliance control.
AI agents call query_compliance to retrieve information from Pentest Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pre-existing compliance mapping data for an engagement. It does not create, modify, delete, or execute operations; it only reads and returns structured information about how findings relate to compliance frameworks (PCI-DSS, HIPAA, SOC2, OWASP). The blast radius of misuse is minimal — an attacker could only access existing compliance metadata, not alter findings or compliance controls.
From the tool's definition Tool description states 'Query compliance mapping' and 'Returns findings grouped by compliance control' — these are retrieval operations with no modification, deletion, or execution of external commands.
Documented attack patterns abuse exactly the kind of access query_compliance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for query_compliance:
{
"version": "1",
"default": "deny",
"tools": {
"query_compliance": {}
}
}query_compliance 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.
Query compliance mapping for an engagement's findings. Frameworks: pci_dss, hipaa, soc2, owasp, all Returns findings grouped by compliance control. It is categorised as a Read tool in the Pentest Ai MCP Server, which means it retrieves data without modifying state.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for query_compliance: 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 Pentest Ai. Nothing to install.
query_compliance 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 query_compliance 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 query_compliance. 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.
query_compliance is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.