get_recent_changes

List all provisions that changed since a given date, with change summaries.

Server German Law MCP Server nenna-ai-gmbh/german-law-mcp
Category Read
Risk class Low
Parameters 00 required

What get_recent_changes does on German Law MCP Server

AI agents call get_recent_changes to retrieve information from German Law MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_recent_changes needs a policy

This tool retrieves and queries information about legal provisions and their modifications over time. It performs a read-only operation with no side effects, data creation, code execution, or destructive actions. The blast radius of misuse is minimal—an agent could only retrieve legislative information that is already public and legally available.

From the tool's definition Tool name 'get_recent_changes' and description 'List all provisions that changed since a given date, with change summaries' indicate a query operation that retrieves historical legislative data without modifying, executing, or deleting anything.

Questions about get_recent_changes

What does the get_recent_changes tool do? +

List all provisions that changed since a given date, with change summaries. It is categorised as a Read tool in the German Law MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_changes? +

Register the German Law MCP Server MCP server in PolicyLayer and add a rule for get_recent_changes: 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 German Law MCP Server. Nothing to install.

What risk level is get_recent_changes? +

get_recent_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_changes? +

Yes. Add a rate_limit block to the get_recent_changes 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.

How do I block get_recent_changes completely? +

Set action: deny in the PolicyLayer policy for get_recent_changes. 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.

What MCP server provides get_recent_changes? +

get_recent_changes is provided by the German Law MCP Server MCP server (nenna-ai-gmbh/german-law-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.