Low Risk

calendario_fiscal

Modelos AEAT y próximos plazos para un código IAE/CNAE. Sin clave.

Risk signalsAccepts freeform code/query input (code)

Part of the Conversor IAE-CNAE server.

calendario_fiscal is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CONVERSOR IAE-CNAE →

Free to start. No card required.

AI agents call calendario_fiscal to retrieve information from Conversor IAE-CNAE without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though calendario_fiscal only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendario_fiscal": {}
  }
}

See the full Conversor IAE-CNAE policy for all 10 tools.

Get this rule live on your own Conversor IAE-CNAE server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CONVERSOR IAE-CNAE →

View all 10 tools →

These attack patterns abuse exactly the kind of access calendario_fiscal gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so calendario_fiscal only ever does what you allow.

SECURE CONVERSOR IAE-CNAE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the calendario_fiscal tool do? +

Modelos AEAT y próximos plazos para un código IAE/CNAE. Sin clave.. It is categorised as a Read tool in the Conversor IAE-CNAE MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendario_fiscal? +

Register the Conversor IAE-CNAE MCP server in PolicyLayer and add a rule for calendario_fiscal: 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 Conversor IAE-CNAE. Nothing to install.

What risk level is calendario_fiscal? +

calendario_fiscal is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit calendario_fiscal? +

Yes. Add a rate_limit block to the calendario_fiscal 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.

How do I block calendario_fiscal completely? +

Set action: deny in the PolicyLayer policy for calendario_fiscal. 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.

What MCP server provides calendario_fiscal? +

calendario_fiscal is provided by the Conversor IAE-CNAE MCP server (https://www.conversoriaecnae.es/api/mcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Conversor IAE-CNAE tool call.

Deterministic rules across all 10 Conversor IAE-CNAE tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.