AI agents call get_symbol to retrieve information from Scholar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored text without modifying, deleting, or executing anything. It is purely a read operation querying the ebook library. The blast radius is minimal - worst case, an agent could retrieve unintended passages, but no data is changed, deleted, or executed. Severity is low as access control should limit what symbols/files are accessible, and reading text alone poses minimal risk.
From the tool's definition Tool description states 'Retrieve the full stored text for a given file and symbol' - the verb 'Retrieve' indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Retrieve the full stored text for a given file and symbol. It is categorised as a Read tool in the Scholar MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP server in PolicyLayer and add a rule for get_symbol: 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 Scholar. Nothing to install.
get_symbol 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_symbol 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_symbol. 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_symbol is provided by the Scholar MCP server (unlomtrois/little-librarian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →