Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination.
AI agents call search_issues 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 retrieves and queries existing issue data from Lychee Redmine using filters and pagination. It has no side effects—it does not create, modify, delete, or execute any operations. The capability is limited to searching and reading project management data, making it a standard Read category tool with low risk.
From the tool's definition Tool name 'search_issues' and description states it 'Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination.' - purely retrieval operation with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination. 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 search_issues: 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.
search_issues 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 search_issues 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 search_issues. 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.
search_issues 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 →