Skip to main content
Glama
Sign In
@palveron/mcp-server

@palveron/mcp-server

by palveron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

palveron_check

Check any tool call against governance policies before execution. Get an allow, block, or modify verdict with PII redacted, plus an immutable audit trail.

Instructions

Verify a tool call against PALVERON governance policies before execution. Returns whether the action is allowed, blocked, or modified (with PII redacted). Every check creates an immutable audit trace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool": "<tool>",
      "input": "<input>"
    },
    "name": "palveron_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe tool name to check (e.g. "execute_command", "write_file", "browser_navigate")
inputYesThe tool input/arguments as a string or JSON string
agent_idNoOptional agent identifier for audit trail
session_idNoOptional session ID for conversation tracking

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully bears the transparency burden. It discloses the return categories (allowed, blocked, modified), PII redaction, and the creation of an immutable audit trace, giving the agent a clear picture of side effects. It does not mention rate limits or failure modes, but for a governance check this is reasonably complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the core action, and each sentence adds value: what it does, what it returns, and the audit side effect. No redundant or vague language is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately simple (4 params, no output schema), and the description covers purpose, usage context, outcome types, and side effects. It lacks explicit examples or detailed return structure, but these are not essential given the schema and the clear description. The description is sufficiently complete for an agent to choose and invoke the tool appropriately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage with descriptions for all four parameters. The description itself does not add parameter-level detail beyond the schema, but it does frame the purpose of the tool/input parameters. This meets the baseline for full schema coverage, with no additional semantics provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a specific verb+resource combination: 'Verify a tool call against PALVERON governance policies before execution.' This clearly distinguishes the tool from siblings like palveron_status and palveron_policy_list, focusing on pre-execution checking rather than status or policy listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before execution' clearly establishes when to use the tool (prior to running a tool call). It also describes the outcome (allowed/blocked/modified) which implies appropriate usage as a gate. However, it does not explicitly name alternatives or provide conditions for when not to use it, so it lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools