list_ticket_provider_observations
Read owner-private retained Jira/Linear status observations and effect evidence, optionally scoped to a ticket/provider. Includes deleted-ticket history. Follow next_before_id while has_more, limit 1–100. Requires tickets:read or tickets:write; no provider request or credential decryption. Histor...
This record as markdown: /tools/com-meta-council-decision-intelligence/list-ticket-provider-observations.md
What list_ticket_provider_observations does on Meta Council
AI agents call list_ticket_provider_observations 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 |
|---|---|---|---|
limit | integer | — | |
provider | string | — | |
before_id | string | — | |
ticket_id | string | — |
Parameters from the server's own tool schema.
Why list_ticket_provider_observations is rated Low
Even though list_ticket_provider_observations 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 list_ticket_provider_observations 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 list_ticket_provider_observations, this is the rule to start with:
list_ticket_provider_observations 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 list_ticket_provider_observations call is checked against it from then on.
Questions about list_ticket_provider_observations
Read owner-private retained Jira/Linear status observations and effect evidence, optionally scoped to a ticket/provider. Includes deleted-ticket history. Follow next_before_id while has_more, limit 1–100. Requires tickets:read or tickets:write; no provider request or credential decryption. Historical checks are not proof of current remote state. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_ticket_provider_observations accepts 4 parameters: limit, provider, before_id, 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 list_ticket_provider_observations: 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.
list_ticket_provider_observations 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 list_ticket_provider_observations 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 list_ticket_provider_observations. 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.
list_ticket_provider_observations 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