Query the local LLM for simple subtasks that require additional context.
AI agents invoke query_local_llm_with_context to trigger actions in Local Llm Delegation. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes queries against a local LLM, passing context and arguments that influence its behavior. This constitutes triggering an external operation whose effects depend on the arguments provided. While not directly destructive or financial, it runs an operation with side effects (LLM inference, potential downstream actions based on results) that goes beyond a simple read.
From the tool's definition 'Query the local LLM for simple subtasks that require additional context' — triggers an external LLM operation with supplied arguments/context
Attacks that exploit this kind of access
Query the local LLM for simple subtasks that require additional context. It is categorised as a Execute tool in the Local Llm Delegation MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Llm Delegation MCP server in PolicyLayer and add a rule for query_local_llm_with_context: 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 Local Llm Delegation. Nothing to install.
query_local_llm_with_context is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_local_llm_with_context 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 query_local_llm_with_context. 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.
query_local_llm_with_context is provided by the Local Llm Delegation MCP server (mrrodriguez/local-llm-delegation-mcp). 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 →