Close an existing Twist thread with an optional closing message. This tool marks a thread as closed, preventing further replies while keeping the thread accessible for reference. A closing message is automatically added to indicate the thread has been closed. Example response: Successfully closed...
AI agents use close_thread to create or update resources in Pointsyeah — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pointsyeah environment.
The tool modifies the state of a thread resource by closing it, which is a write operation. However, since closing a thread does not delete data and is generally reversible (the thread remains accessible), it does not qualify as Destructive.
From the tool's definition Tool description states it 'marks a thread as closed' and 'preventing further replies', indicating a state change to an existing resource. The action is reversible (threads can typically be reopened), distinguishing it from destructive operations.
Attacks that exploit this kind of access
Close an existing Twist thread with an optional closing message. This tool marks a thread as closed, preventing further replies while keeping the thread accessible for reference. A closing message is automatically added to indicate the thread has been closed. Example response: Successfully closed thread: - Thread ID: 789012 - Closing message:. It is categorised as a Write tool in the Pointsyeah MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for close_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 Pointsyeah. Nothing to install.
close_thread 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 close_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.
Set action: deny in the PolicyLayer policy for close_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.
close_thread is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →