AI agents call xcrun_show_sdk_version to retrieve information from Xctools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns SDK version metadata. It performs no side effects, does not execute code, does not modify data, and does not trigger external operations with variable outcomes. It is a straightforward informational retrieval tool analogous to 'get' or 'fetch' operations, fitting the Read category. Severity is low because exposing SDK version information poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'xcrun_show_sdk_version' and description 'Show the version of the SDK' indicate a query operation that retrieves SDK version information without modifying or executing arbitrary code.
Attacks that exploit this kind of access
Show the version of the SDK. It is categorised as a Read tool in the Xctools MCP Server, which means it retrieves data without modifying state.
Register the Xctools MCP server in PolicyLayer and add a rule for xcrun_show_sdk_version: 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 Xctools. Nothing to install.
xcrun_show_sdk_version 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 xcrun_show_sdk_version 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 xcrun_show_sdk_version. 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.
xcrun_show_sdk_version is provided by the Xctools MCP server (nzrsky/xctools-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 →