Return recent tool invocation audit entries from this server instance (in-memory, resets on cold start).
AI agents call get_audit_log to retrieve information from Semantic BI MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical audit log records stored in-memory. It is purely informational—retrieving records of what tools were invoked without the ability to modify, delete, or execute new operations. The blast radius of misuse is minimal: an AI agent could only read audit trail information, which poses no data integrity, operational, or financial risk. Classified as Read with low severity.
From the tool's definition Tool returns 'recent tool invocation audit entries' with no capability to modify, delete, or execute operations. The description explicitly states it retrieves audit log data (query/fetch pattern with no side effects).
Attacks that exploit this kind of access
Return recent tool invocation audit entries from this server instance (in-memory, resets on cold start). It is categorised as a Read tool in the Semantic BI MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic BI 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 Semantic BI MCP. 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 Semantic BI MCP server (lovrobubanic/semantic-bi-mcp). 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 →