Get the result of a Factifai session
AI agents call getFactifaiSessionResult to retrieve information from Factifai 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 the outcome of an existing Factifai testing session. It queries data without modifying, deleting, or executing anything. The minimal blast radius (read-only access to test results) supports a low severity classification.
From the tool's definition Tool name 'getFactifaiSessionResult' and description 'Get the result of a Factifai session' indicate a retrieval operation with no side effects. The verb 'get' and context of retrieving test results confirm this is a query/fetch operation.
Attacks that exploit this kind of access
Get the result of a Factifai session. It is categorised as a Read tool in the Factifai MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Factifai MCP Server MCP server in PolicyLayer and add a rule for getFactifaiSessionResult: 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 Factifai MCP Server. Nothing to install.
getFactifaiSessionResult 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 getFactifaiSessionResult 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 getFactifaiSessionResult. 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.
getFactifaiSessionResult is provided by the Factifai MCP Server MCP server (presidio-oss/factifai-mcp-server). 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 →