AI agents call get_session_status to retrieve information from CHAI pentest tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that queries and retrieves session state and findings data. While it accesses sensitive penetration testing results, it performs no side effects, modifications, or destructive actions. Severity is medium rather than low because the findings data could be sensitive security information that an AI agent could misuse if combined with other tools, but the tool itself is non-destructive.
From the tool's definition Tool name 'get_session_status' and description 'Get session status and findings' indicate data retrieval without modification. Returns information about an active penetration testing session.
Documented attack patterns abuse exactly the kind of access get_session_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CHAI pentest tool, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_status": {}
}
}get_session_status 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 session status and findings. It is categorised as a Read tool in the CHAI pentest tool MCP Server, which means it retrieves data without modifying state.
Register the CHAI pentest tool MCP server in PolicyLayer and add a rule for get_session_status: 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 CHAI pentest tool. Nothing to install.
get_session_status 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_session_status 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_session_status. 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_session_status is provided by the CHAI pentest tool MCP server (nihar-sarkar/chai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CHAI pentest tool, 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.
16 CHAI pentest tool tools catalogued and risk-classified — across an index of 43,000+ MCP servers.