Get a safety and risk analysis for a peptide or combination from the PEPTOMA Safety Agent. Returns: evidence level, known risks, contraindications, potential interactions, unknown gaps, and research disclaimer.
AI agents call check_safety 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 queries and retrieves safety information about peptides from the PEPTOMA Safety Agent. It performs a read-only lookup operation that returns analytical results without modifying any data, executing code, deleting records, or triggering external side effects.
From the tool's definition Tool name 'check_safety' and description indicate it 'Get[s] a safety and risk analysis' and 'Returns: evidence level, known risks, contraindications, potential interactions, unknown gaps, and research disclaimer.' The verb 'Get' and 'Returns' indicate…
Attacks that exploit this kind of access
Get a safety and risk analysis for a peptide or combination from the PEPTOMA Safety Agent. Returns: evidence level, known risks, contraindications, potential interactions, unknown gaps, and research disclaimer. 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 check_safety: 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.
check_safety 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 check_safety 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 check_safety. 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.
check_safety 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 →