fedlex_get_law_history
AI agents call fedlex_get_law_history to retrieve information from Pypi:fedlex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name explicitly uses 'get_law_history', which is a retrieval operation. The description is empty, but the server is purely informational (search, monitor, query legal documents) and all sibling tools are Read operations. There is no evidence of side effects, data modification, code execution, or financial operations. This is a read-only query into legal history records.
From the tool's definition Tool name 'fedlex_get_law_history' combined with server context (Swiss federal law search/query) and sibling tools that are all read-only queries (search_laws, search_treaties, get_recent_publications, get_upcoming_changes) strongly indicate this retrieves…
Attacks that exploit this kind of access
fedlex_get_law_history. It is categorised as a Read tool in the Pypi:fedlex MCP Server, which means it retrieves data without modifying state.
Register the Pypi:fedlex MCP server in PolicyLayer and add a rule for fedlex_get_law_history: 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:fedlex. Nothing to install.
fedlex_get_law_history 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 fedlex_get_law_history 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 fedlex_get_law_history. 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.
fedlex_get_law_history is provided by the Pypi:fedlex MCP server (malkreide/fedlex-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 →