sample_llm
AI agents use sample_llm to create or update resources in MCP Everything — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Everything environment.
An AI agent can call sample_llm faster than any human can review — one bad instruction and it creates or modifies resources in MCP Everything by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
sample_llm. It is categorised as a Write tool in the MCP Everything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Everything MCP server in PolicyLayer and add a rule for sample_llm: 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 Everything. Nothing to install.
sample_llm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sample_llm 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 sample_llm. 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.
sample_llm is provided by the MCP Everything MCP server (s2005/mcp-everything). 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 →