WRITE. Appends an auditable agent action or outcome to the local ATS JSONL ledger, including sources, approvals, output, and whether the task advanced.
AI agents use record_action to create or update resources in Agentic Task System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Task System environment.
The tool creates and appends new data entries to an audit ledger. This is a Write operation because it modifies data reversibly by adding records. Severity is medium because unauthorized modifications to audit logs could obscure agent actions, but the operation appends rather than overwrites, preserving audit trail integrity.
From the tool's definition Tool description explicitly states "WRITE" and "Appends an auditable agent action or outcome to the local ATS JSONL ledger". The action creates/adds new records to a ledger without deleting or overwriting existing entries.
Attacks that exploit this kind of access
WRITE. Appends an auditable agent action or outcome to the local ATS JSONL ledger, including sources, approvals, output, and whether the task advanced. It is categorised as a Write tool in the Agentic Task System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Task System MCP server in PolicyLayer and add a rule for record_action: 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 Agentic Task System. Nothing to install.
record_action 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 record_action 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 record_action. 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.
record_action is provided by the Agentic Task System MCP server (renezander030/agentic-task-system). 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 →