verify_agent

Check an agent's Regent identity/KYA status.

SERVERMarketplace SOURCEhttps://get4agent.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-get4agent-marketplace/verify-agent.md

WHAT IT DOES

What verify_agent does on Marketplace

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

Parameter	Type	Required	Description
`agent_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why verify_agent is rated Low

Even though verify_agent 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_agent safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Marketplace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_agent, this is the rule to start with:

verify_agent Allowed

verify_agent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_agent": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Marketplace, apply this rule, and every verify_agent call is checked against it from then on.

FAQ

Questions about verify_agent

What does the verify_agent tool do? +

Check an agent's Regent identity/KYA status. It is categorised as a Read tool in the Marketplace MCP Server, which means it retrieves data without modifying state.

What parameters does verify_agent accept? +

verify_agent accepts 1 parameter: agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on verify_agent? +

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

What risk level is verify_agent? +

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

Can I rate-limit verify_agent? +

Yes. Add a rate_limit block to the verify_agent 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 verify_agent completely? +

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

verify_agent is provided by the Marketplace MCP server (https://get4agent.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Marketplace, and thousands of servers like it.

This server

All 10 Marketplace tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →