New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

find_licensed_supplier

Licensed parties for a presentation in a jurisdiction (tenant as a parameter). Takes the decision_id of an allow or require_rx decision from gate_transaction.

SERVERA2A-Peptides SOURCEhttps://mcp.a2a-peptides.ai/mcp
Low RISK CLASS
Category Read
Parameters 43 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/a2a-peptides/find-licensed-supplier.md

What find_licensed_supplier does on A2A-Peptides

AI agents call find_licensed_supplier to retrieve information from A2A-Peptides without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
tenant object —
decision_id string Yes
jurisdiction string Yes
presentation_id string Yes

Parameters from the server's own tool schema.

Why find_licensed_supplier is rated Low

Even though find_licensed_supplier only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about find_licensed_supplier

What does the find_licensed_supplier tool do? +

Licensed parties for a presentation in a jurisdiction (tenant as a parameter). Takes the decision_id of an allow or require_rx decision from gate_transaction. It is categorised as a Read tool in the A2A-Peptides MCP Server, which means it retrieves data without modifying state.

What parameters does find_licensed_supplier accept? +

find_licensed_supplier accepts 4 parameters: tenant, decision_id, jurisdiction, presentation_id. Required: decision_id, jurisdiction, presentation_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on find_licensed_supplier? +

Register the A2A-Peptides MCP server in PolicyLayer and add a rule for find_licensed_supplier: 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 A2A-Peptides. Nothing to install.

What risk level is find_licensed_supplier? +

find_licensed_supplier is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_licensed_supplier? +

Yes. Add a rate_limit block to the find_licensed_supplier 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.

How do I block find_licensed_supplier completely? +

Set action: deny in the PolicyLayer policy for find_licensed_supplier. 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.

What MCP server provides find_licensed_supplier? +

find_licensed_supplier is provided by the A2A-Peptides MCP server (https://mcp.a2a-peptides.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on A2A-Peptides, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of A2A-Peptides's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.