Get OpenAPI metadata for a specific operationId (method/path/params/requestBody).
AI agents call astrovisor_openapi_get to retrieve information from Astrovisor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns metadata from the OpenAPI specification. It does not create, modify, delete, or execute any actual operations — it only retrieves documentation/schema information. The blast radius of misuse is minimal since it cannot affect data, trigger external actions, or cause financial harm.
From the tool's definition Tool name contains 'get' and description states it 'Get[s] OpenAPI metadata' — a retrieval operation with no side effects. It fetches schema information about an operation (method/path/params/requestBody) rather than executing or modifying anything.
Documented attack patterns abuse exactly the kind of access astrovisor_openapi_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Astrovisor, and nothing reaches the server without passing your rules. This is the rule we recommend for astrovisor_openapi_get:
{
"version": "1",
"default": "deny",
"tools": {
"astrovisor_openapi_get": {}
}
}astrovisor_openapi_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get OpenAPI metadata for a specific operationId (method/path/params/requestBody). It is categorised as a Read tool in the Astrovisor MCP Server, which means it retrieves data without modifying state.
Register the Astrovisor MCP server in PolicyLayer and add a rule for astrovisor_openapi_get: 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 Astrovisor. Nothing to install.
astrovisor_openapi_get 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 astrovisor_openapi_get 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 astrovisor_openapi_get. 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.
astrovisor_openapi_get is provided by the Astrovisor MCP server (rokoss21/astrovisor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Astrovisor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Astrovisor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.