search_threads_locations

Search Threads’ public place index by name (or by latitude+longitude) and get location ids. Use this when the brand has a PHYSICAL location — a restaurant, salon, gym, store — so the post can be geotagged to it. Pass the chosen id as post_to_meta(locationId) with target:

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/search-threads-locations.md

WHAT IT DOES

What search_threads_locations does on Hermoso

AI agents call search_threads_locations to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_threads_locations is rated Low

Even though search_threads_locations only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_threads_locations safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_threads_locations, this is the rule to start with:

search_threads_locations Allowed

search_threads_locations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every search_threads_locations call is checked against it from then on.

FAQ

Questions about search_threads_locations

What does the search_threads_locations tool do? +

How do I enforce a policy on search_threads_locations? +

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

What risk level is search_threads_locations? +

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

Can I rate-limit search_threads_locations? +

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

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

search_threads_locations is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →