Low Risk

meta_search_places

Searches for Facebook Places (locations) by name or coordinates. Use this to get a location_id for tagging posts, Instagram photos, or Threads. Args: - q (string, optional): Search query (e.g.,

How to control meta_search_places ↓

What meta_search_places does on Meta MCP Server

AI agents call meta_search_places 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 meta_search_places needs a policy

This tool retrieves location data from Meta's Places database to support tagging operations. It is a pure read operation that queries existing data without creating, modifying, or deleting anything. The low severity reflects the limited blast radius—misuse would only return location identifiers that are already public information, posing no risk of data loss, financial harm, or unauthorized state changes.

From the tool's definition Tool description states 'Searches for Facebook Places (locations) by name or coordinates' and is used 'to get a location_id'. The verb 'searches' and 'get' indicate retrieval/query operations with no data modification or side effects.

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

How to control meta_search_places

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

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

meta_search_places 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 meta_search_places

What does the meta_search_places tool do? +

Searches for Facebook Places (locations) by name or coordinates. Use this to get a location_id for tagging posts, Instagram photos, or Threads. Args: - q (string, optional): Search query (e.g.,. 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 meta_search_places? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_search_places: 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 meta_search_places? +

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

Can I rate-limit meta_search_places? +

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

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

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