Low Risk

threads_get_mentions

Gets posts where the authenticated user was @mentioned. Args: - threads_user_id (string): Threads user ID

How to control threads_get_mentions ↓

What threads_get_mentions does on Meta MCP Server

AI agents call threads_get_mentions to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why threads_get_mentions needs a policy

This tool retrieves existing data (mentions/posts) about the authenticated user without modifying, creating, deleting, or executing any actions. It is a straightforward query operation that returns information only. The blast radius of misuse is minimal—an agent could retrieve mentions data but cannot affect accounts, posts, or business operations.

From the tool's definition Tool name 'threads_get_mentions' and description 'Gets posts where the authenticated user was @mentioned' indicate a retrieval operation with no side effects.

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

How to control threads_get_mentions

PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for threads_get_mentions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "threads_get_mentions": {}
  }
}

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

  1. Create a free account and register Meta MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about threads_get_mentions

What does the threads_get_mentions tool do? +

Gets posts where the authenticated user was @mentioned. Args: - threads_user_id (string): Threads user ID. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on threads_get_mentions? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_get_mentions: 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 Meta MCP Server. Nothing to install.

What risk level is threads_get_mentions? +

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

Can I rate-limit threads_get_mentions? +

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

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

threads_get_mentions is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Meta MCP Server tool call.

Start from Meta 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.

200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.