audit_events_legal_holds_configure
Run audit-events.legal-holds.configure through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/audit-events-legal-holds-configure.md
What audit_events_legal_holds_configure does on Appaloft
AI agents use audit_events_legal_holds_configure to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | |
from | string | — | |
reason | string | Yes | |
eventType | string | — | |
aggregateId | string | — | |
requestedBy | string | — |
Parameters from the server's own tool schema.
Why audit_events_legal_holds_configure is rated Medium
An AI agent can call audit_events_legal_holds_configure faster than any human can review: one bad instruction and it creates or modifies resources in Appaloft by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs audit_events_legal_holds_configure 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_configure, this is the rule to start with:
audit_events_legal_holds_configure stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_configure call is checked against it from then on.
Questions about audit_events_legal_holds_configure
Run audit-events.legal-holds.configure through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
audit_events_legal_holds_configure accepts 6 parameters: to, from, reason, eventType, aggregateId, requestedBy. Required: reason. 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_configure: 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_configure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the audit_events_legal_holds_configure 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_configure. 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_configure 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