Low Risk

edict_support

Returns structured sponsorship and support information for the Edict project

Part of the Edict Lang server.

edict_support 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 EDICT LANG →

Free to start. No card required.

AI agents call edict_support to retrieve information from Edict Lang 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 edict_support 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": {
    "edict_support": {}
  }
}

See the full Edict Lang policy for all 22 tools.

Get this rule live on your own Edict Lang server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EDICT LANG →

View all 22 tools →

These attack patterns abuse exactly the kind of access edict_support 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 edict_support only ever does what you allow.

SECURE EDICT LANG →

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

What does the edict_support tool do? +

Returns structured sponsorship and support information for the Edict project. It is categorised as a Read tool in the Edict Lang MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on edict_support? +

Register the Edict Lang MCP server in PolicyLayer and add a rule for edict_support: 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 Edict Lang. Nothing to install.

What risk level is edict_support? +

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

Can I rate-limit edict_support? +

Yes. Add a rate_limit block to the edict_support 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 edict_support completely? +

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

edict_support is provided by the Edict Lang MCP server (edict-lang). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Edict Lang tool call.

Deterministic rules across all 22 Edict Lang 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.