audit_history
THE LAST AUDIT ON FILE FOR AN ACCOUNT, IN FULL. Pass who (an X handle). Rendered from the snapshot's own stored card — what the audit actually concluded, not a re-run. The grade and organic score, the account's followers / following / posts, median engagement units and estimated honest rate, EVER...
This record as markdown: /tools/ai-rokha-rokha/audit-history.md
What audit_history does on Rokha
AI agents call audit_history to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
who | string | Yes |
Parameters from the server's own tool schema.
Why audit_history is rated Low
Retrieves stored audit data for an account; no side effects or modifications.
From the tool's definition THE LAST AUDIT ON FILE... Rendered from the snapshot's own stored card
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs audit_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_history, this is the rule to start with:
audit_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every audit_history call is checked against it from then on.
Questions about audit_history
THE LAST AUDIT ON FILE FOR AN ACCOUNT, IN FULL. Pass who (an X handle). Rendered from the snapshot's own stored card — what the audit actually concluded, not a re-run. The grade and organic score, the account's followers / following / posts, median engagement units and estimated honest rate, EVERY FLAG WITH ITS SIGNED POINT DELTA (the score is their sum — showing them is what makes the number arguable), where the engagement comes from, and Rokha's written read. Audits are informational — since 2026-09-24 they do not change Tailwind scoring. Public, no auth. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
audit_history accepts 1 parameter: who. Required: who. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for audit_history: 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 Rokha. Nothing to install.
audit_history 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_history 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_history. 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_history is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue