Get schedule information for a project in Lychee Redmine. Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis.
AI agents call get_schedule to retrieve information from MCP Server for Lychee Redmine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves schedule information from a Redmine project without creating, modifying, deleting, or executing operations. It is a read-only data retrieval operation with no side effects or blast radius if invoked by an AI agent.
From the tool's definition Tool name 'get_schedule' and description explicitly states it 'Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis' — purely retrieves project schedule data with no modification or side effects.
Attacks that exploit this kind of access
Get schedule information for a project in Lychee Redmine. Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis. It is categorised as a Read tool in the MCP Server for Lychee Redmine MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Lychee Redmine 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 MCP Server for Lychee Redmine. 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 MCP Server for Lychee Redmine MCP server (ssoma-dev/mcp-server-lychee-redmine). 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 →