AI agents use update to create or update resources in Amazon Location Service MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Location Service MCP Server environment.
The tool name 'update' indicates a write operation that creates or modifies data reversibly. Given the AWS Location Service context, this likely modifies geographic or location-related resources. The empty description prevents higher confidence and rules out destructive operations (which would typically be named delete/remove).
From the tool's definition Tool named 'update' with empty description. Based on naming convention and context as an AWS Location Service MCP server, 'update' typically modifies existing data (e.g., location data, geofences, routes). Without explicit description, confidence is reduced.
Documented attack patterns abuse exactly the kind of access update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Location Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update:
{
"version": "1",
"default": "deny",
"tools": {
"update": {
"limits": [
{
"counter": "update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update 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.
update. It is categorised as a Write tool in the Amazon Location Service MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Location Service MCP Server MCP server in PolicyLayer and add a rule for update: 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 Amazon Location Service MCP Server. Nothing to install.
update 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 update 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 update. 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.
update is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Location Service MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Location Service MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.