list_audit_logs

Audit logs are not available on New Central instances.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/list-audit-logs.md

WHAT IT DOES

What list_audit_logs does on API-Central

AI agents call list_audit_logs to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_audit_logs is rated Low

This tool retrieves historical audit log records for review and monitoring purposes, which is a non-destructive data retrieval operation. Although audit logs can contain sensitive information, the tool itself only reads existing data without side effects.

From the tool's definition Tool name 'list_audit_logs' and description indicate retrieval of audit log data with no modification capability. The description notes that audit logs are unavailable on New Central instances, confirming this is a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_audit_logs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_audit_logs, this is the rule to start with:

list_audit_logs Allowed

list_audit_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_audit_logs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every list_audit_logs call is checked against it from then on.

FAQ

Questions about list_audit_logs

What does the list_audit_logs tool do? +

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.

How do I enforce a policy on list_audit_logs? +

Register the API-Central MCP server in PolicyLayer and add a rule for list_audit_logs: 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.

What risk level is list_audit_logs? +

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

Can I rate-limit list_audit_logs? +

Yes. Add a rate_limit block to the list_audit_logs 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 list_audit_logs completely? +

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

list_audit_logs 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.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →