Continue a conversation by sampling the next assistant response
AI agents invoke sampleConversation to trigger actions in MCP Elicitations Demo 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 triggers an LLM sampling operation to generate the next response in a conversation, which constitutes executing an external operation (LLM inference call). The effect depends on the conversation input, and it interacts with an external system (the LLM). It is not a simple read since it actively invokes a generative process, and not purely a write since it doesn't store data.
From the tool's definition Continue a conversation by sampling the next assistant response
Attacks that exploit this kind of access
Continue a conversation by sampling the next assistant response. It is categorised as a Execute tool in the MCP Elicitations Demo Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Elicitations Demo Server MCP server in PolicyLayer and add a rule for sampleConversation: 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 Elicitations Demo Server. Nothing to install.
sampleConversation 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 sampleConversation 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 sampleConversation. 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.
sampleConversation is provided by the MCP Elicitations Demo Server MCP server (soriat/soria-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 →