preview_ticket_export
Preview the exact owned ticket content, destination, correlation marker and status mapping for Jira or Linear. Supply destination (Jira project key or Linear team key) for an unlinked ticket. Returns expected export hash; no provider request or external write. Requires explicit integrations:write...
This record as markdown: /tools/com-meta-council-decision-intelligence/preview-ticket-export.md
What preview_ticket_export does on Meta Council
AI agents use preview_ticket_export 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 |
|---|---|---|---|
provider | string | Yes | |
ticket_id | string | Yes | |
destination | string | — |
Parameters from the server's own tool schema.
Why preview_ticket_export is rated Medium
An AI agent can call preview_ticket_export faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs preview_ticket_export 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 preview_ticket_export, this is the rule to start with:
preview_ticket_export 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 preview_ticket_export call is checked against it from then on.
Questions about preview_ticket_export
Preview the exact owned ticket content, destination, correlation marker and status mapping for Jira or Linear. Supply destination (Jira project key or Linear team key) for an unlinked ticket. Returns expected export hash; no provider request or external write. Requires explicit integrations:write and tickets:write. Review this preview before export; a changed ticket or provider credential needs a fresh preview. 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.
preview_ticket_export accepts 3 parameters: provider, ticket_id, destination. Required: provider, ticket_id. 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 preview_ticket_export: 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.
preview_ticket_export 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 preview_ticket_export 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 preview_ticket_export. 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.
preview_ticket_export 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