check_applicability
Determine which EU regulations apply to an entity based on its sector and optional subsector. Returns a {results, meta} envelope: one cited row per applicable regulation with confidence level (definite / likely / possible), the basis article, contextual notes, and a source_url/publisher/license _...
This record as markdown: /tools/eu-ansvar-eu-regulations-mcp/check-applicability.md
What check_applicability does on Eu Regulations
AI agents call check_applicability to retrieve information from Eu Regulations without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_applicability is rated Low
This tool retrieves and queries information about EU regulations—which ones apply to a given entity—without modifying data, executing code, or causing side effects. It is a lookup/search function that returns informational results (regulations, articles, confidence levels, citations). The confidence reflects clear language indicating read-only retrieval with zero destructive or executable intent.
From the tool's definition Tool description explicitly states it 'Determine[s] which EU regulations apply' and 'Returns a {results, meta} envelope' with cited rows, articles, and contextual notes. No modify, delete, or execute operations mentioned.
Attacks that exploit this kind of access
The rule that runs check_applicability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Eu Regulations, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_applicability, this is the rule to start with:
check_applicability is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Eu Regulations, apply this rule, and every check_applicability call is checked against it from then on.
Questions about check_applicability
Determine which EU regulations apply to an entity based on its sector and optional subsector. Returns a {results, meta} envelope: one cited row per applicable regulation with confidence level (definite / likely / possible), the basis article, contextual notes, and a source_url/publisher/license _citation to the basis provision (or the instrument when the basis article is not provision-addressable). meta carries entity scope + confidence counts; detail_level=summary adds next steps. It is categorised as a Read tool in the Eu Regulations MCP Server, which means it retrieves data without modifying state.
Register the Eu Regulations MCP server in PolicyLayer and add a rule for check_applicability: 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 Eu Regulations. Nothing to install.
check_applicability 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 check_applicability 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 check_applicability. 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.
check_applicability is provided by the Eu Regulations MCP server (https://gateway.ansvar.eu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Eu Regulations, and thousands of servers like it.
This server
Across the catalogue