AI agents call list_analysis_cards to retrieve information from Millimap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read/retrieval operation to enumerate existing analysis cards in the UI. It has no ability to modify data, execute code, delete content, or trigger external processes. The blast radius of misuse is minimal—an agent could only gather information about what analyses are already visible. This clearly maps to the 'Read' category with low severity.
From the tool's definition The tool 'list_analysis_cards' is described as listing analysis result cards visible in MilliMap's workspace sidebar. The verb 'list' is a read operation that retrieves or queries data without modifying or executing anything.
Attacks that exploit this kind of access
List the analysis result cards visible in MilliMap's workspace sidebar. It is categorised as a Read tool in the Millimap MCP Server, which means it retrieves data without modifying state.
Register the Millimap MCP server in PolicyLayer and add a rule for list_analysis_cards: 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 Millimap. Nothing to install.
list_analysis_cards 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_analysis_cards 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_analysis_cards. 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_analysis_cards is provided by the Millimap MCP server (milliomics/millimap-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 →