resolve_discussion
Resolve a discussion thread (resolved: true) or reopen it (resolved: false). Root posts only — replies inherit. Resolving hides the thread from list_discussion by default; nothing is deleted and the posts stay readable with includeResolved. Any member may resolve; resolve when the point is settle...
This record as markdown: /tools/adrata-adrata-mcp/resolve-discussion.md
What resolve_discussion does on Adrata
AI agents use resolve_discussion to create or update resources in Adrata, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adrata environment.
Why resolve_discussion is rated Medium
An AI agent can call resolve_discussion faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs resolve_discussion 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 resolve_discussion, this is the rule to start with:
resolve_discussion stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every resolve_discussion call is checked against it from then on.
Questions about resolve_discussion
Resolve a discussion thread (resolved: true) or reopen it (resolved: false). Root posts only — replies inherit. Resolving hides the thread from list_discussion by default; nothing is deleted and the posts stay readable with includeResolved. Any member may resolve; resolve when the point is settled or absorbed into the body, not to silence it.${GOVERNED_NOTE}. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adrata MCP server in PolicyLayer and add a rule for resolve_discussion: 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.
resolve_discussion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_discussion 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 resolve_discussion. 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.
resolve_discussion 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.
This server
Across the catalogue