epl_gesuchseingaenge
AI agents call epl_gesuchseingaenge to retrieve information from Pypi:bag Epl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it queries or lists request submissions/entries related to health insurance coverage lists. The server is query-focused with no write or destructive capabilities mentioned. Sibling tools are all Read operations (search, lookup, legal context). Without a description, confidence is moderate, but the contextual evidence strongly suggests this retrieves data rather than modifying it.
From the tool's definition Tool name 'epl_gesuchseingaenge' (request entries/submissions) combined with sibling tools that are all query/search oriented (epl_ggsl_abfrage, epl_migel_suche, epl_sl_suche, epl_rechtskontext).
Attacks that exploit this kind of access
epl_gesuchseingaenge. It is categorised as a Read tool in the Pypi:bag Epl MCP Server, which means it retrieves data without modifying state.
Register the Pypi:bag Epl MCP server in PolicyLayer and add a rule for epl_gesuchseingaenge: 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:bag Epl. Nothing to install.
epl_gesuchseingaenge 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 epl_gesuchseingaenge 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 epl_gesuchseingaenge. 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.
epl_gesuchseingaenge is provided by the Pypi:bag Epl MCP server (malkreide/bag-epl-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 →