AI agents use update_schedule_state to create or update resources in Awslabs Amazon Sns Sqs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Amazon Sns Sqs environment.
Based on the verb 'update', this is a Write operation that modifies data (schedule state) reversibly. Confidence is moderate (0.6) due to the empty description—without clarification, we cannot rule out that this modifies critical scheduling behavior that could affect message delivery.
From the tool's definition Tool name is 'update_schedule_state' which suggests modifying state of a schedule, likely within SNS/SQS messaging context. Description is empty, providing no clarification.
Documented attack patterns abuse exactly the kind of access update_schedule_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for update_schedule_state:
{
"version": "1",
"default": "deny",
"tools": {
"update_schedule_state": {
"limits": [
{
"counter": "update_schedule_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_schedule_state 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_schedule_state. It is categorised as a Write tool in the Awslabs Amazon Sns Sqs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for update_schedule_state: 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 Awslabs Amazon Sns Sqs. Nothing to install.
update_schedule_state 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_schedule_state 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_schedule_state. 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_schedule_state is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.