lib_run_across

A execute tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/lib-run-across.md

WHAT IT DOES

What lib_run_across does on Eda Agent

AI agents invoke lib_run_across to trigger actions in Eda Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why lib_run_across is rated High

Likely executes operations across multiple library items; absent description lowers confidence but execution risk is probable.

From the tool's definition uninformative description; 'run_across' suggests batch execution over library items

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lib_run_across safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lib_run_across, this is the rule to start with:

lib_run_across Rate-limited

lib_run_across stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lib_run_across": {
      "limits": [
        {
          "counter": "lib_run_across_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every lib_run_across call is checked against it from then on.

FAQ

Questions about lib_run_across

What does the lib_run_across tool do? +

lib_run_across is a execute tool on the Eda Agent MCP server. It is categorised as a Execute tool in the Eda Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lib_run_across? +

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

What risk level is lib_run_across? +

lib_run_across is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lib_run_across? +

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

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

lib_run_across is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 726 Eda Agent tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →