list_thread_changes

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/list-thread-changes.md

WHAT IT DOES

What list_thread_changes does on Adrata

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

RISK

Why list_thread_changes is rated Low

Even though list_thread_changes 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_thread_changes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_thread_changes, this is the rule to start with:

list_thread_changes Allowed

list_thread_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_thread_changes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every list_thread_changes call is checked against it from then on.

FAQ

Questions about list_thread_changes

What does the list_thread_changes tool do? +

Read the field-change log for one goal, idea, decision or indicator: every PATCH and state move as a row with field, oldValue, newValue, who changed it, when, and the reason — newest first. Never rewritten. This is. 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 list_thread_changes? +

Register the Adrata MCP server in PolicyLayer and add a rule for list_thread_changes: 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 list_thread_changes? +

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

Can I rate-limit list_thread_changes? +

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

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

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

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools →

Across the catalogue

review_changes on MCP Server PR Pilot →list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →