LLM completion requests (streaming and non-streaming)
AI agents invoke Sampling to trigger actions in MCP Server. 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 submits prompts to an external LLM (Azure OpenAI) and retrieves completions. It is not a simple read — it actively triggers external API calls and computation whose outputs depend entirely on the inputs. This qualifies as Execute, since it runs external operations. Misuse could lead to prompt injection, unauthorized API usage, cost escalation, or generation of harmful content.
From the tool's definition LLM completion requests (streaming and non-streaming) — triggers external LLM inference operations via Azure OpenAI integration
Attacks that exploit this kind of access
LLM completion requests (streaming and non-streaming). It is categorised as a Execute tool in the MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server MCP server in PolicyLayer and add a rule for Sampling: 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 MCP Server. Nothing to install.
Sampling 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 Sampling 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 Sampling. 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.
Sampling is provided by the MCP Server MCP server (krishanu-das-05/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →