check_ticket_provider_status
Read the linked Jira/Linear issue status and retain an owner/link/configuration-bound observation. Requires explicit integrations:read and tickets:write. No issue creation, status transition, or automatic recovery of uncertain effects. Inspect the observation and current evidence, then use the or...
This record as markdown: /tools/com-meta-council-decision-intelligence/check-ticket-provider-status.md
What check_ticket_provider_status does on Meta Council
AI agents call check_ticket_provider_status to retrieve information from Meta Council 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 |
|---|---|---|---|
provider | string | Yes | |
ticket_id | string | Yes |
Parameters from the server's own tool schema.
Why check_ticket_provider_status is rated Low
Even though check_ticket_provider_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_ticket_provider_status 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 check_ticket_provider_status, this is the rule to start with:
check_ticket_provider_status 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 Meta Council, apply this rule, and every check_ticket_provider_status call is checked against it from then on.
Questions about check_ticket_provider_status
Read the linked Jira/Linear issue status and retain an owner/link/configuration-bound observation. Requires explicit integrations:read and tickets:write. No issue creation, status transition, or automatic recovery of uncertain effects. Inspect the observation and current evidence, then use the original effect ID for explicit reconciliation if needed. Each deliberate check records new evidence; unavailable or changed bindings remain unknown. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
check_ticket_provider_status accepts 2 parameters: provider, ticket_id. 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 check_ticket_provider_status: 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.
check_ticket_provider_status 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 check_ticket_provider_status 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 check_ticket_provider_status. 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.
check_ticket_provider_status 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