extract_locations · Loc Knowledge Graph Memory Server MCP

WHAT IT DOES

What extract_locations does on Loc Knowledge Graph Memory Server

AI agents use extract_locations to create or update resources in Loc Knowledge Graph Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Loc Knowledge Graph Memory Server environment.

WHY IT NEEDS A POLICY

Why extract_locations needs a policy

This tool both reads input text and writes new entities/relationships to the persistent knowledge graph. The dominant effect is writing (creating new location entities and geographic relationships), making Write the appropriate category. Misuse could result in polluting the knowledge graph with incorrect location data across user conversations, warranting medium severity.

From the tool's definition Extract locations from text and add them to the knowledge graph as entities with geographic relationships

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

extract_locations Rate-limited

extract_locations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_locations": {
      "limits": [
        {
          "counter": "extract_locations_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Loc Knowledge Graph Memory Server, so you can run agents against it safely.

FAQ

Questions about extract_locations

What does the extract_locations tool do? +

Extract locations from text and add them to the knowledge graph as entities with geographic relationships. It is categorised as a Write tool in the Loc Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on extract_locations? +

Register the Loc Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for extract_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 Loc Knowledge Graph Memory Server. Nothing to install.

What risk level is extract_locations? +

extract_locations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit extract_locations? +

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

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

extract_locations is provided by the Loc Knowledge Graph Memory Server MCP server (myangsun/loc-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.