List GLP audit log entries (who did what and when).
AI agents call list_glp_audit_logs 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 queries and retrieves audit log entries for informational purposes only. Reading audit logs has no side effects and presents minimal risk even if misused by an agent, as it only exposes historical records of past actions rather than enabling new operations or data modifications. The blast radius is limited to information disclosure of audit trails.
From the tool's definition Tool name contains 'list' and description explicitly states 'List GLP audit log entries'. The function retrieves historical audit log data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
List GLP audit log entries (who did what and when). 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 list_glp_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.
list_glp_audit_logs 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 list_glp_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.
Set action: deny in the PolicyLayer policy for list_glp_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.
list_glp_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.
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 →