Run a candidate profile against a URL and grade the result with the oracle. ok=true only when a stream was captured AND the oracle confirms it is real media. Iterate on the profile until this passes.
AI agents invoke zahori_test_profile to trigger actions in Zahori. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool actively runs a profile (browser-driven automation) against a target URL, which constitutes executing external operations. It's not purely reading data — it drives a browser, captures streams, and invokes an oracle evaluation.
From the tool's definition 'Run a candidate profile against a URL and grade the result with the oracle' — triggers browser-driven execution against an external URL, running automation logic and evaluating results
Attacks that exploit this kind of access
Run a candidate profile against a URL and grade the result with the oracle. ok=true only when a stream was captured AND the oracle confirms it is real media. Iterate on the profile until this passes. It is categorised as a Execute tool in the Zahori MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zahori MCP server in PolicyLayer and add a rule for zahori_test_profile: 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 Zahori. Nothing to install.
zahori_test_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zahori_test_profile 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 zahori_test_profile. 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.
zahori_test_profile is provided by the Zahori MCP server (josesepulvedapino/zahori). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
zahori_test_profile is one line of Zahori's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →