Every schedule the bridge knows about — active, completed, cancelled, error.
AI agents call list_schedules to retrieve information from Claude Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about schedules without creating, modifying, deleting, or executing anything. It is a straightforward read operation that returns metadata about scheduled work items in the bridge, making it a Read category risk with low severity since viewing schedule status poses minimal security risk.
From the tool's definition Tool name 'list_schedules' and description 'Every schedule the bridge knows about' indicate a query/retrieval operation with no modification of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Every schedule the bridge knows about — active, completed, cancelled, error. It is categorised as a Read tool in the Claude Bridge MCP Server, which means it retrieves data without modifying state.
Register the Claude Bridge MCP server in PolicyLayer and add a rule for list_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 Claude Bridge. Nothing to install.
list_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_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_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_schedules is provided by the Claude Bridge MCP server (josiahsiegel/claude-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →