Low Risk

get_source

Get detailed information about a data source by its ID.

How to control get_source ↓

What get_source does on Financial Reports MCP Server

AI agents call get_source to retrieve information from Financial Reports MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_source needs a policy

This tool retrieves and queries information without modifying, executing, deleting, or committing financial transactions. It has no side effects beyond returning data. The blast radius of misuse is minimal—an agent could only access information about data sources that are already exposed by the API.

From the tool's definition Tool name 'get_source' and description 'Get detailed information about a data source by its ID' indicate retrieval of metadata about a data source. The verb 'Get' and the passive retrieval pattern are characteristic of Read operations.

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

How to control get_source

PolicyLayer is an MCP gateway — it sits between your AI agents and Financial Reports MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_source:

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

get_source 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 Financial Reports MCP Server — 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 get_source

What does the get_source tool do? +

Get detailed information about a data source by its ID. It is categorised as a Read tool in the Financial Reports MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_source? +

Register the Financial Reports MCP Server MCP server in PolicyLayer and add a rule for get_source: 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 Financial Reports MCP Server. Nothing to install.

What risk level is get_source? +

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

Can I rate-limit get_source? +

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

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

get_source is provided by the Financial Reports MCP Server MCP server (itisaevalex/financial-reports-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Financial Reports MCP Server tool call.

Start from Financial Reports MCP Server, 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.

18 Financial Reports MCP Server 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.