AI agents call get_mac_bundle_id to retrieve information from Sl Test without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval only. It extracts a bundle identifier from an existing macOS app bundle, analogous to reading a file property or attribute. There are no destructive, modifying, executing, or financial effects. The worst misuse would be to extract identifiers from multiple apps, which has minimal blast radius.
From the tool's definition Tool description states it 'Extracts the bundle identifier from a macOS app bundle (.app)' - a pure read/query operation that retrieves metadata without modification or side effects.
Attacks that exploit this kind of access
Extracts the bundle identifier from a macOS app bundle (.app). IMPORTANT: You MUST provide the appPath parameter. Example: get_mac_bundle_id({ appPath:. It is categorised as a Read tool in the Sl Test MCP Server, which means it retrieves data without modifying state.
Register the Sl Test MCP server in PolicyLayer and add a rule for get_mac_bundle_id: 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 Sl Test. Nothing to install.
get_mac_bundle_id 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_mac_bundle_id 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_mac_bundle_id. 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_mac_bundle_id is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). 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 →