Low Risk

edict_support

Returns structured sponsorship and support information for the Edict project

Part of the Edict Lang MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

edict-lang Read

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.

io-github-sowiedu-edict.yaml
tools:
  edict_support:
    rules:
      - action: allow

See the full Edict Lang policy for all 22 tools.

Tool Name edict_support
Category Read
Risk Level Low

View all 22 tools →

Agents calling read-class tools like edict_support have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

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? +

Add a rule in your Intercept YAML policy under the tools section for edict_support. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Edict Lang MCP server.

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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Edict Lang

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.