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

get_goal_thread

Read one goal as a THREAD: the goal, its strategies, the initiatives/epics linked to it with their progress counts, the ideas that serve it with their state, the decisions that shaped it with a support/concern/object tally, its indicators with the last 12 readings, and the discussion count.

SERVERAdrata SOURCE@adrata/adrata-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/adrata-adrata-mcp/get-goal-thread.md

What get_goal_thread does on Adrata

AI agents call get_goal_thread to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_goal_thread is rated Low

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

Questions about get_goal_thread

What does the get_goal_thread tool do? +

Read one goal as a THREAD: the goal, its strategies, the initiatives/epics linked to it with their progress counts, the ideas that serve it with their state, the decisions that shaped it with a support/concern/object tally, its indicators with the last 12 readings, and the discussion count. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_goal_thread? +

Register the Adrata MCP server in PolicyLayer and add a rule for get_goal_thread: 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 Adrata. Nothing to install.

What risk level is get_goal_thread? +

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

Can I rate-limit get_goal_thread? +

Yes. Add a rate_limit block to the get_goal_thread 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_goal_thread completely? +

Set action: deny in the PolicyLayer policy for get_goal_thread. 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_goal_thread? +

get_goal_thread is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Adrata, 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 Adrata'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.