List stable AsyncAPI specification versions available as GitHub tags.
AI agents call list_asyncapi_spec_versions to retrieve information from AsyncAPI-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists metadata about available AsyncAPI specification versions from GitHub tags. It performs a query operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal since it only exposes publicly available version information.
From the tool's definition Tool description states it 'List[s] stable AsyncAPI specification versions available as GitHub tags' - a read-only retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List stable AsyncAPI specification versions available as GitHub tags. It is categorised as a Read tool in the AsyncAPI-MCP MCP Server, which means it retrieves data without modifying state.
Register the AsyncAPI- MCP server in PolicyLayer and add a rule for list_asyncapi_spec_versions: 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 AsyncAPI-MCP. Nothing to install.
list_asyncapi_spec_versions 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 list_asyncapi_spec_versions 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 list_asyncapi_spec_versions. 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.
list_asyncapi_spec_versions is provided by the AsyncAPI- MCP server (souvikns/asyncapi-mcp). 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 →