Audit logs are not available on New Central instances.
AI agents call get_audit_log to retrieve information from API-Central 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 records for monitoring and compliance purposes. Despite the limitation that logs may not be available on newer instances, the tool's function is inherently a read operation that queries historical data without modifying, executing, or deleting anything. The severity is low because audit log queries have minimal blast radius and no ability to affect system state or operations.
From the tool's definition Tool name 'get_audit_log' indicates retrieval of audit log data; description states logs are unavailable on new instances, confirming read-only query nature with no side effects.
Attacks that exploit this kind of access
Audit logs are not available on New Central instances. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central 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 API-Central. 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 API-Central MCP server (secure-ssid/centralmcp). 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 →