get_sources

Get the status of all data sources (theGraph, chainlist, chains, slip44)

Server Chains API johnaverse/chains-api
Category Read
Risk class Low
Parameters 00 required

What get_sources does on Chains API

AI agents call get_sources to retrieve information from Chains API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_sources needs a policy

This tool retrieves and reports the status of data sources used by the blockchain chains API. It is a read-only query with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker could only gain visibility into the status of backend data sources, which is non-sensitive operational metadata. It belongs in the Read category with low severity.

From the tool's definition Tool name 'get_sources' and description 'Get the status of all data sources' indicate a query operation that retrieves metadata about data source availability/status. No modification, deletion, or external execution is performed.

Risk signalsBulk/mass operation — affects multiple targets

Questions about get_sources

What does the get_sources tool do? +

Get the status of all data sources (theGraph, chainlist, chains, slip44). It is categorised as a Read tool in the Chains API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sources? +

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

What risk level is get_sources? +

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

Can I rate-limit get_sources? +

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

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

get_sources is provided by the Chains API MCP server (johnaverse/chains-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.