AI agents call list_app_schedules to retrieve information from Amazon ECS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix is a strong indicator of a Read category operation—it retrieves and displays data without side effects. Even without explicit description, listing application schedules is a non-destructive query. The context (AWS ECS MCP Server for automation) supports that this would be a configuration inspection tool. Low severity due to read-only nature with minimal blast radius if misused.
From the tool's definition Tool name 'list_app_schedules' indicates a retrieval operation that queries existing schedules without modification. The lack of descriptive text prevents higher confidence, but the verb 'list' is unambiguously a read operation.
Documented attack patterns abuse exactly the kind of access list_app_schedules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_app_schedules:
{
"version": "1",
"default": "deny",
"tools": {
"list_app_schedules": {}
}
}list_app_schedules is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_app_schedules. It is categorised as a Read tool in the Amazon ECS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for list_app_schedules: 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 ECS MCP Server. Nothing to install.
list_app_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_app_schedules 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 list_app_schedules. 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.
list_app_schedules is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.