tyts_validate
Чи приймає редактор повний TytsDocument (без рендера).
This record as markdown: /tools/3rtools-tyts-mcp/tyts-validate.md
What tyts_validate does on Tyts
AI agents call tyts_validate to retrieve information from Tyts without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
document | object | Yes |
Parameters from the server's own tool schema.
Why tyts_validate is rated Low
Even though tyts_validate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs tyts_validate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tyts, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tyts_validate, this is the rule to start with:
tyts_validate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tyts, apply this rule, and every tyts_validate call is checked against it from then on.
Questions about tyts_validate
Чи приймає редактор повний TytsDocument (без рендера). It is categorised as a Read tool in the Tyts MCP Server, which means it retrieves data without modifying state.
tyts_validate accepts 1 parameter: document. Required: document. The full parameter table on this page comes from the server's own tool schema.
Register the Tyts MCP server in PolicyLayer and add a rule for tyts_validate: 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 Tyts. Nothing to install.
tyts_validate 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 tyts_validate 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 tyts_validate. 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.
tyts_validate is provided by the Tyts MCP server (@3rtools/tyts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tyts, and thousands of servers like it.
This server
Across the catalogue