Get MCP interoperability conventions and parameter profiles for LLM clients.
AI agents call astrovisor_conventions 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 tool queries and retrieves metadata about MCP conventions and parameter profiles. It performs a data retrieval operation with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal — an agent could only access documentation or configuration information.
From the tool's definition Tool name contains 'Get' and description states 'Get MCP interoperability conventions and parameter profiles' — retrieves configuration/convention data without side effects.
Documented attack patterns abuse exactly the kind of access astrovisor_conventions 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_conventions:
{
"version": "1",
"default": "deny",
"tools": {
"astrovisor_conventions": {}
}
}astrovisor_conventions 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 MCP interoperability conventions and parameter profiles for LLM clients. 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_conventions: 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_conventions 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_conventions 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_conventions. 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_conventions 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.