Add a file attachment (including images) to a thought
AI agents use add_file_attachment to create or update resources in TheBrain MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TheBrain MCP Server environment.
This tool creates or modifies data (attaches files to thoughts) without permanently destroying information. It is reversible via delete_attachment, making it a Write operation rather than Destructive. The severity is medium because an AI agent could attach malicious, sensitive, or unwanted files to thoughts in a knowledge management system, but the impact is confined to that system and attachments can be removed.
From the tool's definition Tool name 'add_file_attachment' and description 'Add a file attachment (including images) to a thought' indicate file attachment creation/modification. Related tool 'delete_attachment' confirms write/destructive operations exist on this server.
Documented attack patterns abuse exactly the kind of access add_file_attachment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TheBrain MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_file_attachment:
{
"version": "1",
"default": "deny",
"tools": {
"add_file_attachment": {
"limits": [
{
"counter": "add_file_attachment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_file_attachment 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.
Free to start. No card required.
Add a file attachment (including images) to a thought. It is categorised as a Write tool in the TheBrain MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TheBrain MCP Server MCP server in PolicyLayer and add a rule for add_file_attachment: 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 TheBrain MCP Server. Nothing to install.
add_file_attachment 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 add_file_attachment 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 add_file_attachment. 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.
add_file_attachment is provided by the TheBrain MCP Server MCP server (redmorestudio/thebrain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TheBrain MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 TheBrain MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.