AI agents call milestones_get to retrieve information from Testomatio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves milestone data by ID from the Testomatio test management platform. It performs a read-only query operation without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an agent could retrieve unwanted milestone information, but cannot alter test data or trigger external actions. This is a standard Read category tool.
From the tool's definition Tool name 'milestones_get' and description 'Get milestone by ID' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access milestones_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Testomatio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for milestones_get:
{
"version": "1",
"default": "deny",
"tools": {
"milestones_get": {}
}
} milestones_get 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.
Get milestone by ID. It is categorised as a Read tool in the Testomatio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Testomatio MCP Server MCP server in PolicyLayer and add a rule for milestones_get: 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 Testomatio MCP Server. Nothing to install.
milestones_get 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 milestones_get 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 milestones_get. 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.
milestones_get is provided by the Testomatio MCP Server MCP server (testomatio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Testomatio MCP Server, 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.
10 Testomatio MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.