tail_build_log

Last N lines of console output for a build (debug failures).

Server Netlinq Jenkins radhakrishna0018/netlinq-jenkins-mcp
Category Read
Risk class Low
Parameters 00 required

What tail_build_log does on Netlinq Jenkins

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

Why tail_build_log needs a policy

This tool retrieves read-only log/console output from a build. It has no side effects — it simply fetches the last N lines of output for diagnostic purposes. No data is modified, executed, or deleted.

From the tool's definition Last N lines of console output for a build (debug failures)

Questions about tail_build_log

What does the tail_build_log tool do? +

Last N lines of console output for a build (debug failures). It is categorised as a Read tool in the Netlinq Jenkins MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tail_build_log? +

Register the Netlinq Jenkins MCP server in PolicyLayer and add a rule for tail_build_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 Netlinq Jenkins. Nothing to install.

What risk level is tail_build_log? +

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

Can I rate-limit tail_build_log? +

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

Set action: deny in the PolicyLayer policy for tail_build_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 tail_build_log? +

tail_build_log is provided by the Netlinq Jenkins MCP server (radhakrishna0018/netlinq-jenkins-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.