llm_evaluate_coherence

Evalúa la coherencia del modelo ejecutando el mismo prompt múltiples veces

Server LLM MCP Bridge ramgeart/llm-mcp-bridge
Category Execute
Risk class High
Parameters 00 required

What llm_evaluate_coherence does on LLM MCP Bridge

AI agents invoke llm_evaluate_coherence to trigger actions in LLM MCP Bridge. 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.

Why llm_evaluate_coherence needs a policy

The tool executes multiple LLM API requests to evaluate coherence, making it an Execute-category action. It triggers external operations (API calls) whose scope depends on arguments like prompt content and repetition count. Misuse could lead to excessive API usage or costs, warranting medium severity.

From the tool's definition 'ejecutando el mismo prompt múltiples veces' (runs the same prompt multiple times) — the tool actively triggers repeated external LLM API calls

Questions about llm_evaluate_coherence

What does the llm_evaluate_coherence tool do? +

Evalúa la coherencia del modelo ejecutando el mismo prompt múltiples veces. It is categorised as a Execute tool in the LLM MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on llm_evaluate_coherence? +

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

What risk level is llm_evaluate_coherence? +

llm_evaluate_coherence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit llm_evaluate_coherence? +

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

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

llm_evaluate_coherence is provided by the LLM MCP Bridge MCP server (ramgeart/llm-mcp-bridge). 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.