Call any AstroVisor API operation by operationId. Supports compact serialization and follow-up retrieval by resultId.
AI agents invoke astrovisor_request to trigger actions in Astrovisor. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool is a generic API executor that can invoke any operation on the AstroVisor API by operationId. Since it can call 'any' operation, it potentially spans Read, Write, Destructive, and even Financial categories depending on what operationId is passed. Per the rules, when a tool spans categories, pick the most severe applicable.
From the tool's definition "Call any AstroVisor API operation by operationId" - this tool can trigger any arbitrary API operation, not limited to read-only actions
Documented attack patterns abuse exactly the kind of access astrovisor_request 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_request:
{
"version": "1",
"default": "deny",
"tools": {
"astrovisor_request": {
"limits": [
{
"counter": "astrovisor_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}astrovisor_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Call any AstroVisor API operation by operationId. Supports compact serialization and follow-up retrieval by resultId. It is categorised as a Execute tool in the Astrovisor MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Astrovisor MCP server in PolicyLayer and add a rule for astrovisor_request: 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_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the astrovisor_request 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_request. 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_request 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.