Low Risk

get_build_targets

Get all build targets (libraries, executables) from the build system.

How to control get_build_targets ↓

AI agents call get_build_targets to retrieve information from Srclight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns build target information from the build system without creating, modifying, executing, or deleting anything. It is a pure information retrieval operation with no side effects, fitting the Read category. Severity is low because exposing build target names carries minimal risk — they are typically public metadata and don't directly enable harmful actions.

From the tool's definition Tool name is 'get_build_targets' and description states 'Get all build targets' — a retrieval operation with no modification or execution semantics. The verb 'Get' and passive description indicate read-only access to build system metadata.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_build_targets": {}
  }
}

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

  1. Create a free account and register Srclight — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_build_targets tool do? +

Get all build targets (libraries, executables) from the build system. It is categorised as a Read tool in the Srclight MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_build_targets? +

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

What risk level is get_build_targets? +

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

Can I rate-limit get_build_targets? +

Yes. Add a rate_limit block to the get_build_targets 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_targets completely? +

Set action: deny in the PolicyLayer policy for get_build_targets. 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_targets? +

get_build_targets is provided by the Srclight MCP server (srclight/srclight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Srclight tool call.

Deterministic rules across all 42 Srclight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42 Srclight tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.