AI agents invoke ask_model to trigger actions in Proxima. 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.
This tool dispatches requests to external AI providers dynamically based on user-supplied arguments (provider name + message). It executes outbound API calls with variable, argument-driven behavior, making it Execute category. Misuse could result in unintended provider calls or data exfiltration to third-party AI systems, warranting medium severity.
From the tool's definition 'send a message to ANY enabled provider by name' and 'Universal chat' — triggers external AI provider operations whose effects depend on arguments
Attacks that exploit this kind of access
Universal chat: send a message to ANY enabled provider by name (the 4 session providers OR any configured BYOK provider). Use this when you need a provider other than the four dedicated ask_* tools. It is categorised as a Execute tool in the Proxima MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxima MCP server in PolicyLayer and add a rule for ask_model: 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 Proxima. Nothing to install.
ask_model 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 ask_model 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 ask_model. 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.
ask_model is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ask_model is one line of Proxima's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →