Connection test — returns current server time if MaStR SOAP service is reachable.
AI agents call get_local_time 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.
This is a simple read operation that queries the availability and time of a remote service. It has no capability to modify, delete, or execute arbitrary operations. The blast radius of misuse is minimal — an attacker could at most confirm service availability or measure latency. No data is created, modified, or destroyed.
From the tool's definition Tool description states it "returns current server time if MaStR SOAP service is reachable" — this is a diagnostic/connectivity check that retrieves and returns server time without any side effects or data modification.
Attacks that exploit this kind of access
Connection test — returns current server time if MaStR SOAP service is reachable. 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_local_time: 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_local_time 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_local_time 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_local_time. 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_local_time 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 →