AI agents call dev-test-tool as a supporting operation in Icloud workflows.
The description is essentially empty/truncated ('Returns' with no further detail), making it impossible to determine what this tool actually does. Given the sibling tools are all calendar CRUD operations, this may be a development/testing utility, but there is no evidence to assign a meaningful risk category. Defaulting to Other with low confidence due to lack of description.
From the tool's definition Tool description is 'Returns' — uninformative and incomplete, providing no actionable detail about what the tool does.
Attacks that exploit this kind of access
Returns. It is categorised as a Other tool in the Icloud MCP Server, which means it performs auxiliary operations.
Register the Icloud MCP server in PolicyLayer and add a rule for dev-test-tool: 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 Icloud. Nothing to install.
dev-test-tool is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dev-test-tool 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 dev-test-tool. 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.
dev-test-tool is provided by the Icloud MCP server (thefredlab/icloud-mcp). 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 →