AI agents call get_issue_by_id 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 by ID with no side effects. It does not create, modify, delete, or execute operations. It belongs in the Read category with low severity since it only accesses existing data.
From the tool's definition Tool name is 'get_issue_by_id' and description states 'Fetch a single issue by its ID from Magnet and return it as markdown'. The verb 'Fetch' and the return-only behavior indicate data retrieval without modification.
Attacks that exploit this kind of access
Fetch a single issue by its ID from Magnet and return it as markdown. The 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 get_issue_by_id: 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.
get_issue_by_id 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_issue_by_id 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_issue_by_id. 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_issue_by_id 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 →