AI agents call org_info to retrieve information from NetworksDB-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves organizational information from the NetworksDB API without side effects. It is a query operation analogous to 'org_search' on the same server. Read operations that fetch public or semi-public network intelligence data pose minimal risk when misused by an AI agent—the worst outcome is information disclosure or excessive API usage, not data modification or financial impact.
From the tool's definition Tool name 'org_info' and description 'Get information about an organization' indicate a retrieval operation. The server description emphasizes 'queries' and 'organization details', which are read-only intelligence operations.
Documented attack patterns abuse exactly the kind of access org_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NetworksDB-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for org_info:
{
"version": "1",
"default": "deny",
"tools": {
"org_info": {}
}
}org_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about an organization. It is categorised as a Read tool in the NetworksDB-MCP MCP Server, which means it retrieves data without modifying state.
Register the NetworksDB- MCP server in PolicyLayer and add a rule for org_info: 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 NetworksDB-MCP. Nothing to install.
org_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the org_info 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.
Set action: deny in the PolicyLayer policy for org_info. 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.
org_info is provided by the NetworksDB- MCP server (mordavid/networksdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NetworksDB-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 NetworksDB-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.