Detail view of one schedule. Includes last_job_id so you can
AI agents call get_schedule 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 a schedule without modifying, deleting, or executing operations. It is a simple query operation that returns existing data (schedule details and job references). The low severity reflects that unauthorized access to schedule metadata poses minimal risk compared to tools that execute code or modify state.
From the tool's definition Tool name is 'get_schedule' and description indicates it provides a 'detail view of one schedule' with reference to retrieving 'last_job_id'. The verb 'get' and the word 'view' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Detail view of one schedule. Includes last_job_id so you can. 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 get_schedule: 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.
get_schedule 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 get_schedule 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 get_schedule. 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.
get_schedule 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 →