proj_get_nets

A read tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/proj-get-nets.md

WHAT IT DOES

What proj_get_nets does on Eda Agent

AI agents call proj_get_nets to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why proj_get_nets is rated Low

This tool retrieves project net data without modifying state. The 'get' verb and project inspection context indicate a read-only operation. Confidence is reduced from 0.85 to 0.75 due to empty description, but the naming pattern relative to sibling tools strongly suggests read-only semantics. No write, execute, financial, or destructive implications evident.

From the tool's definition Tool name 'proj_get_nets' follows the read-pattern convention (get_*) and retrieves nets from a project. The 'proj_' namespace indicates project inspection.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proj_get_nets 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 proj_get_nets, this is the rule to start with:

proj_get_nets Allowed

proj_get_nets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proj_get_nets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about proj_get_nets

What does the proj_get_nets tool do? +

proj_get_nets is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proj_get_nets? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_get_nets: 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 proj_get_nets? +

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

Can I rate-limit proj_get_nets? +

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

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

proj_get_nets 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 345 Eda Agent tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →