Check the status of a deepfake analysis session.
AI agents call check-session-status to retrieve information from Proofly MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves state information about a previously initiated deepfake analysis session. It does not modify, delete, or execute any operations—it merely reads and reports status. This is a straightforward Read category tool with low severity, as the worst case is retrieving metadata about an analysis that an unauthorized party might already have access to.
From the tool's definition The tool 'check-session-status' retrieves the status of an existing analysis session. The description explicitly states it 'Check[s] the status', which is a query operation with no side effects.
Attacks that exploit this kind of access
Check the status of a deepfake analysis session. It is categorised as a Read tool in the Proofly MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Proofly MCP Integration MCP server in PolicyLayer and add a rule for check-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 Proofly MCP Integration. Nothing to install.
check-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 check-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 check-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.
check-session-status is provided by the Proofly MCP Integration MCP server (prooflie/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →