audit_events_export_global
Read audit-events.export-global through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/audit-events-export-global.md
What audit_events_export_global does on Appaloft
AI agents call audit_events_export_global to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | |
from | string | Yes | |
limit | integer | — | |
order | string | — | |
action | object | — | |
cursor | string | — | |
actorId | object | — | |
eventType | string | — | |
projectId | string | — | |
aggregateId | string | — | |
resourceType | object | — | |
organizationId | string | — |
Parameters from the server's own tool schema.
Why audit_events_export_global is rated Low
The tool description starts with 'Read', suggesting it retrieves/exports audit event data without modifying or deleting anything. However, 'export' could involve writing to external storage; the explicit 'Read' qualifier and the pattern of sibling tools (separate create/list/prune tools exist for archives) suggests this is a read/query operation.
From the tool's definition 'Read audit-events.export-global' — description explicitly starts with 'Read', indicating data retrieval
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs audit_events_export_global safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_events_export_global, this is the rule to start with:
audit_events_export_global 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 Appaloft, apply this rule, and every audit_events_export_global call is checked against it from then on.
Questions about audit_events_export_global
Read audit-events.export-global through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
audit_events_export_global accepts 12 parameters: to, from, limit, order, action, cursor, actorId, eventType, projectId, aggregateId, resourceType, organizationId. Required: to, from. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for audit_events_export_global: 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 Appaloft. Nothing to install.
audit_events_export_global 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 audit_events_export_global 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 audit_events_export_global. 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.
audit_events_export_global is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue