get_build_step_log

THE RISK

Low Risk

Why get_build_step_log needs a policy

The 'get' prefix and 'log' suffix indicate this tool retrieves build step logs from Codemagic's CI/CD system. Logs are read-only artifacts that document build execution. Reading logs has no side effects and causes no data modification or system changes. This is a typical Read operation common in CI/CD platforms for audit and debugging purposes.

From the tool's definition Tool name 'get_build_step_log' clearly indicates a retrieval operation (get) for build logs, which is read-only data access. No description provided, but the name and context of a CI/CD system strongly suggest log querying with no side effects.

Documented attack patterns abuse exactly the kind of access get_build_step_log gives an agent:

POLICY

How to control get_build_step_log

PolicyLayer is an MCP gateway — it sits between your AI agents and Codemagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_build_step_log:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_build_step_log": {}
  }
}

get_build_step_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Codemagic MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Codemagic MCP Server tools

Destructive delete_all_app_caches Delete all stored caches for an application. Destructive delete_app_cache Delete a specific cache from an application. Destructive delete_team_member Remove a team member from the team. Execute cancel_build Cancel a running build on Codemagic. Execute start_build start_build Write add_application Add a new application to Codemagic. Write add_application_private add_application_private Write create_public_artifact_url create_public_artifact_url

All 16 Codemagic MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_build_step_log

What does the get_build_step_log tool do? +

get_build_step_log. It is categorised as a Read tool in the Codemagic MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_build_step_log? +

Register the Codemagic MCP Server MCP server in PolicyLayer and add a rule for get_build_step_log: 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 Codemagic MCP Server. Nothing to install.

What risk level is get_build_step_log? +

get_build_step_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_build_step_log? +

Yes. Add a rate_limit block to the get_build_step_log 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.

How do I block get_build_step_log completely? +

Set action: deny in the PolicyLayer policy for get_build_step_log. 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.

What MCP server provides get_build_step_log? +

get_build_step_log is provided by the Codemagic MCP Server MCP server (stefanoamorelli/codemagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codemagic MCP Server tool call.

Start from Codemagic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →