Read the local AgentBridge audit log. Filter by manifest URL with the optional
AI agents call get_audit_log to retrieve information from AgentBridge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves audit log data for inspection and filtering purposes. It has no capability to modify, delete, or execute operations—it only queries existing historical records. The severity is low because audit logs are typically read-access data with minimal blast radius if exposed, though information disclosure is a minor risk in some contexts.
From the tool's definition Tool description explicitly states "Read the local AgentBridge audit log" with optional filtering capability.
Attacks that exploit this kind of access
Read the local AgentBridge audit log. Filter by manifest URL with the optional. It is categorised as a Read tool in the AgentBridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentBridge MCP Server MCP server in PolicyLayer and add a rule for get_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 AgentBridge MCP Server. Nothing to install.
get_audit_log 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_audit_log is provided by the AgentBridge MCP Server MCP server (marmar9615-cloud/agentbridge-protocol). 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 →