AI agents call list_issues to retrieve information from Magnet 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 issue data from Magnet without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, fitting the 'Read' category. The severity is low because listing issues poses minimal risk—it only exposes existing organizational data that the authenticated user should already have access to.
From the tool's definition Tool name is 'list_issues' and description states 'List all issues for your organization in Magnet'. The verb 'list' and the read-only nature of retrieving issues without modification indicates a retrieval operation.
Attacks that exploit this kind of access
List all issues for your organization in Magnet with markdown content. The organization is determined automatically from your API key. Each issue includes a. It is categorised as a Read tool in the Magnet MCP Server, which means it retrieves data without modifying state.
Register the Magnet MCP server in PolicyLayer and add a rule for list_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 Magnet. Nothing to install.
list_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 list_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 list_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.
list_issues is provided by the Magnet MCP server (@magnet-ai/magnet-mcp-server). 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 →