New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_ticket_projects

Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root tickets). Read-only, recomputed live. Use this before pla...

SERVERMeta Council SOURCEhttps://meta-council.com/mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/get-ticket-projects.md

What get_ticket_projects does on Meta Council

AI agents call get_ticket_projects 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.

Why get_ticket_projects is rated Low

Even though get_ticket_projects 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.

Risk signalsAdmin/system-level operation

Questions about get_ticket_projects

What does the get_ticket_projects tool do? +

Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root tickets). Read-only, recomputed live. Use this before planning a session to see initiative health at a glance; use ticket_list/ticket_get to drill into any id it returns. Refuses more than 10,000 source tickets, 500 emitted root/sub-epic entries or a 256 KiB UTF-8 result; never returns partial totals. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ticket_projects? +

Register the Meta Council MCP server in PolicyLayer and add a rule for get_ticket_projects: 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.

What risk level is get_ticket_projects? +

get_ticket_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ticket_projects? +

Yes. Add a rate_limit block to the get_ticket_projects 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.

How do I block get_ticket_projects completely? +

Set action: deny in the PolicyLayer policy for get_ticket_projects. 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.

What MCP server provides get_ticket_projects? +

get_ticket_projects 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Council's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.