AI agents call example_counter to retrieve information from Virtualization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although 'increments' technically modifies internal state, the tool is explicitly labeled 'example' and 'simple counter,' indicating it is a demonstration/example utility rather than a production operation. It has no destructive, financial, or Execute-class impact on VMs, sandboxes, or external systems.
From the tool's definition Tool name is 'example_counter' with description stating it 'increments on each call.' This is a stateless or simple utility that reads and returns a counter value; despite the word 'increments,' the operation is a benign demonstration tool with no side…
Documented attack patterns abuse exactly the kind of access example_counter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Virtualization, and nothing reaches the server without passing your rules. This is the rule we recommend for example_counter:
{
"version": "1",
"default": "deny",
"tools": {
"example_counter": {}
}
}example_counter 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.
A simple counter that increments on each call. It is categorised as a Read tool in the Virtualization MCP Server, which means it retrieves data without modifying state.
Register the Virtualization MCP server in PolicyLayer and add a rule for example_counter: 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 Virtualization. Nothing to install.
example_counter 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 example_counter 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 example_counter. 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.
example_counter is provided by the Virtualization MCP server (sandraschi/virtualization-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Virtualization, 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.
56 Virtualization tools catalogued and risk-classified — across an index of 43,000+ MCP servers.