node_location

Get the current GPS location from a mobile companion device. Returns latitude, longitude, and accuracy.

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/node-location.md

WHAT IT DOES

What node_location does on CoWork OS

AI agents call node_location 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 node_location is rated Low

GPS location retrieval is fundamentally a read-only operation that queries state without modifying or affecting any system. While location data can be sensitive from a privacy perspective, from a functional MCP tool classification standpoint this is purely informational retrieval.

From the tool's definition Tool description states it 'Get[s] the current GPS location from a mobile companion device. Returns latitude, longitude, and accuracy.' This is a data retrieval operation with no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_location 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 node_location, this is the rule to start with:

node_location Allowed

node_location 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": {
    "node_location": {}
  }
}

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 node_location call is checked against it from then on.

FAQ

Questions about node_location

What does the node_location tool do? +

Get the current GPS location from a mobile companion device. Returns latitude, longitude, and accuracy. 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 node_location? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for node_location: 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 node_location? +

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

Can I rate-limit node_location? +

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

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

node_location 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

The MCP Attack Database →

Guides

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