Low Risk

get_entity_sources

Get all sources linked to specific entities with optional filtering.

How to control get_entity_sources ↓

What get_entity_sources does on literateMCP

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

Low Risk

Why get_entity_sources needs a policy

This tool retrieves and queries linked sources for given entities. It performs a read-only operation on the literature management database. The optional filtering parameter allows refined queries but does not introduce side effects or modification capabilities. No financial transactions, code execution, data destruction, or irreversible changes are involved.

From the tool's definition Tool name 'get_entity_sources' and description 'Get all sources linked to specific entities with optional filtering' indicate retrieval of existing data with no modification, deletion, or execution of arbitrary code.

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

How to control get_entity_sources

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

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

get_entity_sources 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 literateMCP — 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_entity_sources

What does the get_entity_sources tool do? +

Get all sources linked to specific entities with optional filtering. It is categorised as a Read tool in the literateMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_entity_sources? +

Register the literate MCP server in PolicyLayer and add a rule for get_entity_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 literateMCP. Nothing to install.

What risk level is get_entity_sources? +

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

Can I rate-limit get_entity_sources? +

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

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

get_entity_sources is provided by the literate MCP server (zongmin-yu/sqlite-literature-management-fastmcp-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 literateMCP tool call.

Start from literateMCP, 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.

15 literateMCP 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.