AI agents call simuler_holding to retrieve information from Impots without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on available context, this tool appears to simulate tax scenarios for holding structures, which is a computational/analytical operation with no persistent side effects on real data or systems. It reads tax parameters and returns calculated results. However, confidence is reduced due to incomplete description.
From the tool's definition Tool name 'simuler_holding' (simulate holding) and server context indicate a simulation/calculation tool. Description is truncated ('Simule l') and uninformative, preventing full assessment.
Documented attack patterns abuse exactly the kind of access simuler_holding gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Impots, and nothing reaches the server without passing your rules. This is the rule we recommend for simuler_holding:
{
"version": "1",
"default": "deny",
"tools": {
"simuler_holding": {}
}
}simuler_holding 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.
Simule l. It is categorised as a Read tool in the Impots MCP Server, which means it retrieves data without modifying state.
Register the Impots MCP server in PolicyLayer and add a rule for simuler_holding: 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 Impots. Nothing to install.
simuler_holding 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 simuler_holding 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 simuler_holding. 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.
simuler_holding is provided by the Impots MCP server (w4zu/impots-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Impots, 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.
62 Impots tools catalogued and risk-classified — across an index of 43,000+ MCP servers.