audit_events_legal_holds_show
Read audit-events.legal-holds.show through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/audit-events-legal-holds-show.md
What audit_events_legal_holds_show does on Appaloft
AI agents call audit_events_legal_holds_show 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 |
|---|---|---|---|
holdId | string | Yes |
Parameters from the server's own tool schema.
Why audit_events_legal_holds_show is rated Low
This tool retrieves or queries legal hold audit event data with no side effects. The 'show' action and 'Read' designation in the description confirm it is a read-only operation that returns information about legal holds, consistent with the Read category of tools that retrieve data without making changes.
From the tool's definition Tool description explicitly states 'Read audit-events.legal-holds.show' and is described as reading/showing legal hold information without modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs audit_events_legal_holds_show 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_legal_holds_show, this is the rule to start with:
audit_events_legal_holds_show 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_legal_holds_show call is checked against it from then on.
Questions about audit_events_legal_holds_show
Read audit-events.legal-holds.show 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_legal_holds_show accepts 1 parameter: holdId. Required: holdId. 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_legal_holds_show: 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_legal_holds_show 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_legal_holds_show 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_legal_holds_show. 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_legal_holds_show 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