Low Risk

crow_audit_log

Return recent audit log entries for a project space, ordered newest first.

How to control crow_audit_log ↓

What crow_audit_log does on Crow

AI agents call crow_audit_log to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why crow_audit_log needs a policy

This tool retrieves historical audit log information for read-only purposes. It does not modify, delete, or execute any operations. While audit logs may contain sensitive information about project activities, the tool itself only reads and returns data without side effects, making it a Read category tool.

From the tool's definition Tool description states 'Return recent audit log entries' - this is a retrieval operation with no side effects. The verb 'return' indicates querying existing audit log data.

Documented attack patterns abuse exactly the kind of access crow_audit_log gives an agent:

How to control crow_audit_log

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_audit_log:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_audit_log": {}
  }
}

crow_audit_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_audit_log

What does the crow_audit_log tool do? +

Return recent audit log entries for a project space, ordered newest first. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_audit_log? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_audit_log: 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 Crow. Nothing to install.

What risk level is crow_audit_log? +

crow_audit_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crow_audit_log? +

Yes. Add a rate_limit block to the crow_audit_log 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.

How do I block crow_audit_log completely? +

Set action: deny in the PolicyLayer policy for crow_audit_log. 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.

What MCP server provides crow_audit_log? +

crow_audit_log is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.