AI agents call get_analysis to retrieve information from Peptoma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing analysis data by ID and returns results without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on a research platform's data store. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes previously computed analysis data.
From the tool's definition Tool name 'get_analysis' and description 'Retrieve a previously completed PEPTOMA sequence analysis' indicate data retrieval with no modification or execution. The phrase 'Returns the full analysis result' confirms it is a query operation with no side effects.
Attacks that exploit this kind of access
Retrieve a previously completed PEPTOMA sequence analysis by its numeric ID. Returns the full analysis result including all AI-generated metrics and community annotation counts. It is categorised as a Read tool in the Peptoma MCP Server, which means it retrieves data without modifying state.
Register the Peptoma MCP server in PolicyLayer and add a rule for get_analysis: 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 Peptoma. Nothing to install.
get_analysis 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_analysis 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_analysis. 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_analysis is provided by the Peptoma MCP server (peptoma/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 →