AI agents call boe_nomenaments to retrieve information from Mcp Govern without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the context of a transparency/anti-corruption investigation server focused on 'cross-referencing open data' and analyzing public records, boe_nomenaments almost certainly retrieves or queries Spanish government appointment data from BOE (Boletín Oficial del Estado). No write, destructive, execute, or financial capabilities are evident from the name or server purpose.
From the tool's definition Tool name 'boe_nomenaments' (BOE appointments/nominations) suggests querying public government appointment records. No description provided to clarify exact function.
Documented attack patterns abuse exactly the kind of access boe_nomenaments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Govern, and nothing reaches the server without passing your rules. This is the rule we recommend for boe_nomenaments:
{
"version": "1",
"default": "deny",
"tools": {
"boe_nomenaments": {}
}
}boe_nomenaments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
boe_nomenaments. It is categorised as a Read tool in the Mcp Govern MCP Server, which means it retrieves data without modifying state.
Register the Mcp Govern MCP server in PolicyLayer and add a rule for boe_nomenaments: 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 Mcp Govern. Nothing to install.
boe_nomenaments 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 boe_nomenaments 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 boe_nomenaments. 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.
boe_nomenaments is provided by the Mcp Govern MCP server (xavimf87/mcp-govern). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Govern, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
49 Mcp Govern tools catalogued and risk-classified — across an index of 43,000+ MCP servers.