Log a completion or a re-watch/re-read/re-listen with a date. Use when the user mentions finishing something again ("watched Heat again last night", "reread Dune"). The first finish is tracked by status; this records repeats so they show in history and stats.
Part of the Achriom server.
Free to start. No card required.
AI agents call log_event to retrieve information from Achriom without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though log_event only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"log_event": {}
}
}See the full Achriom policy for all 33 tools.
These attack patterns abuse exactly the kind of access log_event gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Log a completion or a re-watch/re-read/re-listen with a date. Use when the user mentions finishing something again ("watched Heat again last night", "reread Dune"). The first finish is tracked by status; this records repeats so they show in history and stats.. It is categorised as a Read tool in the Achriom MCP Server, which means it retrieves data without modifying state.
Register the Achriom MCP server in PolicyLayer and add a rule for log_event: 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 Achriom. Nothing to install.
log_event 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 log_event 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 log_event. 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.
log_event is provided by the Achriom MCP server (https://mcp.achriom.com/mcp?api_key={api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 Achriom tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.