Given a goal (metabolic, longevity, recovery, cosmetic, cognitive, sleep, libido, hormonal, immune, gut) and region (ISO-3166-1 alpha-2 or Panya legacy code), returns the top 3 vendors from Panya's 11-signal-vetted catalog with rubric scores, monthly USD price bands, supply state, risk band, and ...
Part of the Panya — peptide vendor matchmaker server.
Free to start. No card required.
AI agents call panya.match_vendor to retrieve information from Panya — peptide vendor matchmaker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though panya.match_vendor only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"panya.match_vendor": {}
}
}See the full Panya — peptide vendor matchmaker policy for all 3 tools.
These attack patterns abuse exactly the kind of access panya.match_vendor gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Given a goal (metabolic, longevity, recovery, cosmetic, cognitive, sleep, libido, hormonal, immune, gut) and region (ISO-3166-1 alpha-2 or Panya legacy code), returns the top 3 vendors from Panya's 11-signal-vetted catalog with rubric scores, monthly USD price bands, supply state, risk band, and citation links. Useful for: cross-border GLP-1 cost comparison, Thailand peptide sourcing, Bali medical-tourism research, UK NHS Wegovy waitlist alternatives.. It is categorised as a Read tool in the Panya — peptide vendor matchmaker MCP Server, which means it retrieves data without modifying state.
Register the Panya — peptide vendor matchmaker MCP server in PolicyLayer and add a rule for panya.match_vendor: 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 Panya — peptide vendor matchmaker. Nothing to install.
panya.match_vendor 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 panya.match_vendor 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 panya.match_vendor. 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.
panya.match_vendor is provided by the Panya — peptide vendor matchmaker MCP server (https://panya.health/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Panya — peptide vendor matchmaker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.