get_tags

THE RISK

Low Risk

Why get_tags needs a policy

This tool queries and retrieves existing tags from a knowledge management system. It performs no creation, modification, deletion, or execution of external operations. The operation is read-only and carries minimal risk if misused by an AI agent.

From the tool's definition Tool name 'get_tags' and description 'Get all tags in a brain' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_tags gives an agent:

POLICY

How to control get_tags

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 get_tags:

policy.json

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

get_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register TheBrain MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More TheBrain MCP Server tools

Destructive delete_attachment Delete an attachment Destructive delete_link Delete a link Destructive delete_thought Delete a thought Write append_to_note Append content to an existing note Write add_file_attachment Add a file attachment (including images) to a thought Write add_url_attachment Add a URL attachment to a thought Write create_link Create a link between two thoughts with visual properties Write create_or_update_note Create or update a note with markdown content

All 26 TheBrain MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_tags

What does the get_tags tool do? +

Get all tags in a brain. It is categorised as a Read tool in the TheBrain MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tags? +

Register the TheBrain MCP Server MCP server in PolicyLayer and add a rule for get_tags: 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.

What risk level is get_tags? +

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

Can I rate-limit get_tags? +

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

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

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

Enforce policy on every TheBrain MCP Server tool call.

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.

CHECK YOUR STACK →