Validate a candidate skill document before installation.
AI agents call validate_skill_markdown to retrieve information from Friday MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes data (a skill document) to verify its format or correctness before any installation occurs. It has no side effects, does not execute code, does not modify or delete data, and does not commit financial obligations. It is purely a Read operation: inspection/validation of existing content.
From the tool's definition Tool name and description indicate validation/inspection only: 'Validate a candidate skill document before installation.' No modification, execution, deletion, or financial operations occur—only parsing and checking a markdown document.
Attacks that exploit this kind of access
Validate a candidate skill document before installation. It is categorised as a Read tool in the Friday MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Friday MCP Server MCP server in PolicyLayer and add a rule for validate_skill_markdown: 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 Friday MCP Server. Nothing to install.
validate_skill_markdown is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_skill_markdown 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 validate_skill_markdown. 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.
validate_skill_markdown is provided by the Friday MCP Server MCP server (jeremylakeyjr/mcp-server). 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 →