Compare iOS vs Android element snapshots against a checklist of named spatial relationships (vertical centering, baseline/left alignment, equal gap/size, presence, truncation) and flag per-relation match/mismatch/uncertain — catches cross-platform layout drift like status text centered on one pla...
AI agents call audit_parity to retrieve information from Raven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ios | object | Yes | |
android | object | Yes | |
checklist | array | Yes |
Parameters from the server's own tool schema.
This tool performs design audit/analysis by comparing UI layouts across platforms and reporting on spatial relationship mismatches. It retrieves and analyzes data without modifying any system state, executing code, or triggering external side effects. The 'audit' family of sibling tools on this server are all inspection/validation tools, consistent with Read category classification.
From the tool's definition Tool description indicates it 'Compare[s]' snapshots 'against a checklist' and 'flag[s]' results—purely analytical operations. No create, modify, delete, execute, or financial operations mentioned.
Risk signalsHigh parameter count (32 properties)
Attacks that exploit this kind of access
Compare iOS vs Android element snapshots against a checklist of named spatial relationships (vertical centering, baseline/left alignment, equal gap/size, presence, truncation) and flag per-relation match/mismatch/uncertain — catches cross-platform layout drift like status text centered on one platform but top-aligned on the other. Provide ios+android {elements,viewport} snapshots and a checklist[]. It is categorised as a Read tool in the Raven MCP Server, which means it retrieves data without modifying state.
audit_parity accepts 3 parameters: ios, android, checklist. Required: ios, android, checklist. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for audit_parity: 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 Raven. Nothing to install.
audit_parity 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 audit_parity 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 audit_parity. 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.
audit_parity is provided by the Raven MCP server (raven-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 →