Return the detailed read-only contract for exactly one declared provider CLI subcommand.
AI agents call provider_subcommand_contract to retrieve information from LLM CLI Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema or contract metadata for a CLI subcommand without modifying state, executing code, or triggering side effects. It is a straightforward information-retrieval (Read) operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name and description indicate 'Return the detailed read-only contract' — a retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access provider_subcommand_contract gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for provider_subcommand_contract:
{
"version": "1",
"default": "deny",
"tools": {
"provider_subcommand_contract": {}
}
}provider_subcommand_contract 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.
Return the detailed read-only contract for exactly one declared provider CLI subcommand. It is categorised as a Read tool in the LLM CLI Gateway MCP Server, which means it retrieves data without modifying state.
Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for provider_subcommand_contract: 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 LLM CLI Gateway. Nothing to install.
provider_subcommand_contract 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 provider_subcommand_contract 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 provider_subcommand_contract. 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.
provider_subcommand_contract is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LLM CLI Gateway, 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.
46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.