Score how agent-ready a URL is. Returns a 0–100 score, structured checks, and grouped recommendations.
AI agents call scan_agent_readiness to retrieve information from AgentBridge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic scan that retrieves information and produces a score/assessment. It has no side effects—it does not create, modify, delete, execute code, or commit financial transactions. The output is purely informational (score, checks, recommendations), consistent with Read category operations like query, list, and get.
From the tool's definition Tool name 'scan_agent_readiness' and description 'Score how agent-ready a URL is. Returns a 0–100 score, structured checks, and grouped recommendations' indicate a read-only assessment function that queries and returns data about URL readiness without…
Attacks that exploit this kind of access
Score how agent-ready a URL is. Returns a 0–100 score, structured checks, and grouped recommendations. It is categorised as a Read tool in the AgentBridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentBridge MCP Server MCP server in PolicyLayer and add a rule for scan_agent_readiness: 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 AgentBridge MCP Server. Nothing to install.
scan_agent_readiness 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 scan_agent_readiness 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 scan_agent_readiness. 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.
scan_agent_readiness is provided by the AgentBridge MCP Server MCP server (marmar9615-cloud/agentbridge-protocol). 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 →