AI agents call get_source_entities 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.
This is a read-only retrieval operation that queries existing relationships in the database without creating, modifying, or deleting any data. The 'get_' prefix and absence of mutation language confirm it is a passive read operation with minimal risk even if misused.
From the tool's definition Tool retrieves 'all entities linked to multiple sources' with no modification verbs; the action is purely query-based data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_source_entities gives an agent:
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_source_entities:
{
"version": "1",
"default": "deny",
"tools": {
"get_source_entities": {}
}
}get_source_entities 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 all entities linked to multiple sources. It is categorised as a Read tool in the literateMCP MCP Server, which means it retrieves data without modifying state.
Register the literate MCP server in PolicyLayer and add a rule for get_source_entities: 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.
get_source_entities 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 get_source_entities 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 get_source_entities. 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.
get_source_entities 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.
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.