AI agents call uxpass_report_json to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes | The run id returned by uxpass_run |
Parameters from the server's own tool schema.
The tool fetches a pre-existing JSON report for a UXPass run. This is a read-only retrieval operation with no side effects. Low severity since it only exposes report data, not sensitive financial or destructive capabilities.
From the tool's definition 'Get the JSON report for a UXPass run' — purely retrieves/queries existing report data
Attacks that exploit this kind of access
Get the JSON report for a UXPass run. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
uxpass_report_json accepts 1 parameter: run_id. Required: run_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for uxpass_report_json: 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 UnClick. Nothing to install.
uxpass_report_json 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 uxpass_report_json 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 uxpass_report_json. 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.
uxpass_report_json is provided by the UnClick MCP server (@unclick/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 →