Import a specific thread by its provider thread ID (e.g., Gmail thread ID from search_messages). If the thread already exists locally, syncs it instead. Use after search_messages when get_thread_by_external_id returns 'not found'. Requires 'threads:sync' permission.
Part of the TextForge server.
Free to start. No card required.
AI agents use import_thread to create or modify resources in TextForge. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call import_thread repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach TextForge.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"import_thread": {
"limits": [
{
"counter": "import_thread_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full TextForge policy for all 22 tools.
These attack patterns abuse exactly the kind of access import_thread gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Import a specific thread by its provider thread ID (e.g., Gmail thread ID from search_messages). If the thread already exists locally, syncs it instead. Use after search_messages when get_thread_by_external_id returns 'not found'. Requires 'threads:sync' permission.. It is categorised as a Write tool in the TextForge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TextForge MCP server in PolicyLayer and add a rule for import_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 TextForge. Nothing to install.
import_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 import_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 import_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.
import_thread is provided by the TextForge MCP server (textforge/textforge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 TextForge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.