AI agents use add_map_line to create or update resources in OSM PostgreSQL Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OSM PostgreSQL Server environment.
Adding a line to a map is a reversible modification operation that creates new data (a line geometry object). This aligns with the Write category—similar to add_map_marker and add_map_polygon on the same server. Severity is medium because misuse could clutter or alter the visual map display, but the effect is typically reversible.
From the tool's definition Tool name 'add_map_line' suggests creating or modifying map geometry. Sibling tools include 'add_map_marker' and 'add_map_polygon' which are clearly Write operations. The description is empty, requiring inference from naming and server context.
Documented attack patterns abuse exactly the kind of access add_map_line gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OSM PostgreSQL Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_map_line:
{
"version": "1",
"default": "deny",
"tools": {
"add_map_line": {
"limits": [
{
"counter": "add_map_line_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_map_line 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.
Free to start. No card required.
add_map_line. It is categorised as a Write tool in the OSM PostgreSQL Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OSM PostgreSQL Server MCP server in PolicyLayer and add a rule for add_map_line: 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 OSM PostgreSQL Server. Nothing to install.
add_map_line is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_map_line 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.
Set action: deny in the PolicyLayer policy for add_map_line. 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.
add_map_line is provided by the OSM PostgreSQL Server MCP server (wiseman/osm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 OSM PostgreSQL Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 OSM PostgreSQL Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.