AI agents invoke score_gene_signature to trigger actions in Millimap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the name, this tool likely computes/scores a gene signature against the active dataset — a computational operation with side effects on the analysis state. In the context of sibling tools like run_clustering and run_millimap_tool, it likely executes an analysis rather than just reading data. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'score_gene_signature' and server context (MilliMap session with datasets, clusters, annotations, markers). Description is empty.
Attacks that exploit this kind of access
score_gene_signature. It is categorised as a Execute tool in the Millimap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Millimap MCP server in PolicyLayer and add a rule for score_gene_signature: 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.
score_gene_signature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the score_gene_signature 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 score_gene_signature. 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.
score_gene_signature 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 →