get_recent_changes
AI agents call get_recent_changes to retrieve information from MaStR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name follows a 'get_*' pattern consistent with query/retrieval operations. Given the server's purpose as a public energy market register and the absence of any indication of data modification or destruction, this appears to be a read-only operation to retrieve recent changes from the register. Confidence is reduced to 0.75 due to the empty description; with more detail it could be higher.
From the tool's definition Tool name 'get_recent_changes' indicates a retrieval operation; sibling tools on the MaStR server include other read-only query operations like 'get_actor', 'get_unit', 'search_actors_public', suggesting a consistent pattern of data retrieval without…
Attacks that exploit this kind of access
get_recent_changes. It is categorised as a Read tool in the MaStR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MaStR 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 MaStR MCP Server. Nothing to install.
get_recent_changes 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 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.
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.
get_recent_changes is provided by the MaStR MCP Server MCP server (UliRCS/mastr-mcp-server). 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 →