Comprehensive enumeration and exposure scoring of all detected subdomains for a domain
AI agents call subdomain_exposure_scorer to retrieve information from APIMesh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and enumerates subdomain information (reconnaissance), which is a Read operation with no write, execute, or destructive capabilities. Severity is medium because subdomain enumeration results could inform an attacker's reconnaissance phase, though the tool itself only retrieves information.
From the tool's definition Tool performs "enumeration and exposure scoring of all detected subdomains" - a query/discovery operation that retrieves and analyzes existing subdomain data without modifying systems.
Attacks that exploit this kind of access
Comprehensive enumeration and exposure scoring of all detected subdomains for a domain. It is categorised as a Read tool in the APIMesh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the APIMesh MCP Server MCP server in PolicyLayer and add a rule for subdomain_exposure_scorer: 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 APIMesh MCP Server. Nothing to install.
subdomain_exposure_scorer 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 subdomain_exposure_scorer 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 subdomain_exposure_scorer. 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.
subdomain_exposure_scorer is provided by the APIMesh MCP Server MCP server (mbeato/apimesh). 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 →