get_audit_log
Use this to inspect activity history when investigating suspicious access, building a compliance report, or showing a user what they did. Filter by action (VIEW|DOWNLOAD|UPLOAD|LOGIN|DELETE), user_id, or date range.
This record as markdown: /tools/8vdx1-fundos-mcp/get-audit-log.md
What get_audit_log does on Fundos
AI agents call get_audit_log to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_audit_log is rated Low
get_audit_log retrieves audit trail information for compliance and investigation purposes. While audit logs themselves contain sensitive operational data (user actions, access patterns, deletions), the tool is fundamentally a Read operation—it queries existing records without altering system state.
From the tool's definition Tool description states 'inspect activity history' and 'Filter by action (VIEW|DOWNLOAD|UPLOAD|LOGIN|DELETE)' — the core function is querying and retrieving audit log records, not modifying them. No side effects beyond data retrieval.
Attacks that exploit this kind of access
The rule that runs get_audit_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_audit_log, this is the rule to start with:
get_audit_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fundos, apply this rule, and every get_audit_log call is checked against it from then on.
Questions about get_audit_log
Use this to inspect activity history when investigating suspicious access, building a compliance report, or showing a user what they did. Filter by action (VIEW|DOWNLOAD|UPLOAD|LOGIN|DELETE), user_id, or date range. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos 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 Fundos. 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 Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue