Low Risk

key_info

Get information about your NetworksDB API key and usage statistics.

How to control key_info ↓

What key_info does on NetworksDB-MCP

AI agents call key_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.

Low Risk

Why key_info needs a policy

This tool queries and retrieves information about the API key and usage statistics. It performs a read-only operation that returns data without modifying, deleting, or executing any actions. The low severity reflects minimal blast radius—an AI agent misusing this tool would only access metadata about the API key itself and usage metrics, causing no operational impact.

From the tool's definition Tool name 'key_info' and description 'Get information about your NetworksDB API key and usage statistics' indicate retrieval of metadata and usage data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access key_info gives an agent:

How to control key_info

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 key_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "key_info": {}
  }
}

key_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NetworksDB-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about key_info

What does the key_info tool do? +

Get information about your NetworksDB API key and usage statistics. It is categorised as a Read tool in the NetworksDB-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on key_info? +

Register the NetworksDB- MCP server in PolicyLayer and add a rule for key_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.

What risk level is key_info? +

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

Can I rate-limit key_info? +

Yes. Add a rate_limit block to the key_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.

How do I block key_info completely? +

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

What MCP server provides key_info? +

key_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.

Enforce policy on every NetworksDB-MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.