sync_accounting_tickets
Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets. The expected_plan_hash from the preview is required, retries are idempotent, stable references prevent duplicate tickets across reprocessed runs, and human edits to generated ...
This record as markdown: /tools/com-meta-council-decision-intelligence/sync-accounting-tickets.md
What sync_accounting_tickets does on Meta Council
AI agents use sync_accounting_tickets to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes | |
expected_plan_hash | string | Yes | Exact plan_hash returned by preview_accounting_ticket_sync. |
Parameters from the server's own tool schema.
Why sync_accounting_tickets is rated Medium
Creates or updates planning tickets from accounting write-off data, reversibly but with broad data exposure.
From the tool's definition Commit previewed WRITEOff work plan to stable owner-private tickets
Attacks that exploit this kind of access
The rule that runs sync_accounting_tickets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_accounting_tickets, this is the rule to start with:
sync_accounting_tickets 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 Meta Council, apply this rule, and every sync_accounting_tickets call is checked against it from then on.
Questions about sync_accounting_tickets
Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets. The expected_plan_hash from the preview is required, retries are idempotent, stable references prevent duplicate tickets across reprocessed runs, and human edits to generated content fields are preserved. Status, assignee, hierarchy, and completion are not reset. Requires both accounting:read and tickets:write. This creates or updates only in-platform planning tickets; they are not field-encrypted and become readable through tickets:read without accounting:read. It never files, pays, sends, or publishes anything. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sync_accounting_tickets accepts 2 parameters: run_id, expected_plan_hash. Required: run_id, expected_plan_hash. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for sync_accounting_tickets: 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 Meta Council. Nothing to install.
sync_accounting_tickets 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 sync_accounting_tickets 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 sync_accounting_tickets. 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.
sync_accounting_tickets is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue