AI agents use add_map_marker 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.
The tool adds markers to a map, which is a reversible modification of map data. This creates new visual elements but does not delete, execute code, or move money. Confidence is moderate because the description is empty, but sibling tools and server description provide strong contextual evidence of write-like behavior.
From the tool's definition Tool name 'add_map_marker' combined with sibling tools 'add_map_line' and 'add_map_polygon' that modify map state, plus server description stating 'tools for adding markers, polygons' indicates this creates new map objects.
Documented attack patterns abuse exactly the kind of access add_map_marker 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_marker:
{
"version": "1",
"default": "deny",
"tools": {
"add_map_marker": {
"limits": [
{
"counter": "add_map_marker_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_map_marker 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_marker. 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_marker: 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_marker 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_marker 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_marker. 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_marker 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.