Checks whether the YAFL share link at the given url is still live — live, expired, or not found — without downloading or decrypting anything. Returns liveness, size, and expiry only. Does not read the decryption key even if present in the URL fragment, and never fetches any file bytes.
AI agents call get_status to retrieve information from Yafldev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | A YAFL share URL, e.g. https://yafl.dev/t/{id}#{key} (the fragment/key is ignored by this tool) |
Parameters from the server's own tool schema.
The tool performs a read-only status check on a share link without downloading, modifying, executing, or deleting anything. It retrieves metadata (liveness status, size, expiry) about a remote resource. This is a classic Read category operation—query/check with no side effects. Severity is low because the information returned is limited to status and metadata, not sensitive file contents.
From the tool's definition Tool description explicitly states it 'Checks whether the YAFL share link...is still live' and 'Returns liveness, size, and expiry only.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Checks whether the YAFL share link at the given url is still live — live, expired, or not found — without downloading or decrypting anything. Returns liveness, size, and expiry only. Does not read the decryption key even if present in the URL fragment, and never fetches any file bytes. It is categorised as a Read tool in the Yafldev MCP Server, which means it retrieves data without modifying state.
get_status accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Yafldev MCP server in PolicyLayer and add a rule for get_status: 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 Yafldev. Nothing to install.
get_status 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 get_status 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 get_status. 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.
get_status is provided by the Yafldev MCP server (@yafldev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_status is one line of Yafldev's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →