maps.place_details

Fetch normalized details for a place returned by maps.search_places

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/maps.place-details.md

WHAT IT DOES

What maps.place_details does on CoWork OS

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

RISK

Why maps.place_details is rated Low

This tool retrieves read-only information about a place (likely address, hours, ratings, contact info, etc.). It performs a lookup query on existing data without creating, modifying, deleting, or executing code. The blast radius of misuse is minimal—worst case, an agent could retrieve details about sensitive locations, but cannot alter state or trigger external actions.

From the tool's definition Tool description states 'Fetch normalized details for a place' — the verb 'fetch' indicates a retrieval operation with no modification or side effects. The tool queries details about an already-identified place.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs maps.place_details safely

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

maps.place_details Allowed

maps.place_details 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": {
    "maps.place_details": {}
  }
}

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

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

FAQ

Questions about maps.place_details

What does the maps.place_details tool do? +

Fetch normalized details for a place returned by maps.search_places. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on maps.place_details? +

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

What risk level is maps.place_details? +

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

Can I rate-limit maps.place_details? +

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

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

maps.place_details is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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