check_ticket_provider_fields
Explicitly read five native fields for an existing owned link revision. Requires integrations:read and tickets:write. Reserve before I/O; retry exact request_id/arguments to recover its original result without another provider call. Changed link or credential refuses. Unsupported/missing fields a...
This record as markdown: /tools/com-meta-council-decision-intelligence/check-ticket-provider-fields.md
What check_ticket_provider_fields does on Meta Council
AI agents call check_ticket_provider_fields 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 | |
request_id | string | Yes | |
expected_revision | integer | Yes |
Parameters from the server's own tool schema.
Why check_ticket_provider_fields is rated Low
Even though check_ticket_provider_fields 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_fields 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_fields, this is the rule to start with:
check_ticket_provider_fields 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_fields call is checked against it from then on.
Questions about check_ticket_provider_fields
Explicitly read five native fields for an existing owned link revision. Requires integrations:read and tickets:write. Reserve before I/O; retry exact request_id/arguments to recover its original result without another provider call. Changed link or credential refuses. Unsupported/missing fields and noncomparable native formats stay unknown. No remote writes or automatic reconciliation. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
check_ticket_provider_fields accepts 4 parameters: provider, ticket_id, request_id, expected_revision. Required: provider, ticket_id, request_id, expected_revision. 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_fields: 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_fields 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_fields 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_fields. 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_fields 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