AI agents use test_report to create or update resources in Phantom — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Phantom environment.
This tool manages automatic test reports, which involves creating and writing report data (including screenshots) to storage. It's a Write operation as it generates/modifies report files. Confidence is moderate because the description is truncated and partially in French, leaving some ambiguity about full functionality. No destructive, financial, or execution capabilities are evident from the available description.
From the tool's definition Gère le rapport de test automatique. Le rapport démarre AUTOMATIQUEMENT dès la première interaction
Attacks that exploit this kind of access
Gère le rapport de test automatique. Le rapport démarre AUTOMATIQUEMENT dès la première interaction (tap, type_text, etc.) — tu n. It is categorised as a Write tool in the Phantom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Phantom MCP server in PolicyLayer and add a rule for test_report: 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 Phantom. Nothing to install.
test_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the test_report 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 test_report. 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.
test_report is provided by the Phantom MCP server (nthimpulse/phantom-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 →