AI agents call get_trending 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 performs a read-only query of existing data from the PEPTOMA platform. It retrieves and ranks peptide sequences based on community engagement metrics without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an AI agent could only retrieve public trending data, which poses no security, safety, or financial risk.
From the tool's definition Tool retrieves trending peptide sequences ranked by community votes. Uses language: 'Get the top 10 trending peptide sequences' — retrieval/query operation with no modification or execution. No side effects described.
Attacks that exploit this kind of access
Get the top 10 trending peptide sequences on PEPTOMA ranked by community vote count. These are the sequences receiving the most scientific attention from the global research community right now. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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 →