fedlex_search_laws
AI agents call fedlex_search_laws 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.
This tool retrieves or queries Swiss federal law data. Search operations are non-destructive, non-modifying reads. The consistent pattern across sibling tools and the server's stated purpose (search and monitor legal content) confirms read-only semantics. Severity is low because misuse would only expose publicly available legal information without operational impact.
From the tool's definition Tool name 'fedlex_search_laws' indicates a search operation. Server description emphasizes 'search the SR' (Swiss legal compilation) and all sibling tools are read-only queries (get_law_by_sr, get_law_history, get_recent_publications, get_upcoming_changes,…
Attacks that exploit this kind of access
fedlex_search_laws. 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_search_laws: 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_search_laws 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_search_laws 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_search_laws. 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_search_laws 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 →