AI agents call get_group to retrieve information from Redmine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves group information from Redmine. It has no capability to create, modify, delete, or execute operations. The inclusion of related data does not constitute a write or execute action. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_group' with description 'Get a group by id'. The verb 'Get' and the retrieval pattern indicate a query operation with no side effects. The 'include' parameter allows selecting related data (users, memberships) but does not modify anything.
Attacks that exploit this kind of access
Get a group by id. include may contain: users, memberships. It is categorised as a Read tool in the Redmine MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP server in PolicyLayer and add a rule for get_group: 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 Redmine. Nothing to install.
get_group 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_group 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_group. 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_group is provided by the Redmine MCP server (KalvadTech/redmine-mcp). 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 →