erara_get_record
AI agents call erara_get_record to retrieve information from Pypi:swiss Academic Libraries without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (gets) a single record from the e-rara collection. 'Get' operations are read-only queries with no side effects. No creation, modification, deletion, code execution, or financial transaction is implied. The empty description slightly reduces confidence, but the name and server purpose establish this as a retrieval operation.
From the tool's definition Tool name 'erara_get_record' indicates retrieval of a single record from e-rara (a digitized rare books collection). The server description emphasizes 'search and retrieve bibliographic and digitized records' without modification.
Attacks that exploit this kind of access
erara_get_record. It is categorised as a Read tool in the Pypi:swiss Academic Libraries MCP Server, which means it retrieves data without modifying state.
Register the Pypi:swiss Academic Libraries MCP server in PolicyLayer and add a rule for erara_get_record: 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 Pypi:swiss Academic Libraries. Nothing to install.
erara_get_record 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 erara_get_record 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 erara_get_record. 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.
erara_get_record is provided by the Pypi:swiss Academic Libraries MCP server (malkreide/swiss-academic-libraries-mcp). 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 →