get_metadata

Get metadata for a file or folder.

Server Yadisk patr56/yadisk-mcp
Category Read
Risk class Low
Parameters 00 required

What get_metadata does on Yadisk

AI agents call get_metadata to retrieve information from Yadisk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_metadata needs a policy

This tool retrieves metadata (file properties, attributes, timestamps, etc.) without modifying, deleting, or executing anything. It is a straightforward read operation. Severity is low because metadata exposure has minimal blast radius — metadata alone does not compromise data integrity or trigger destructive actions.

From the tool's definition Tool name is 'get_metadata' and description states 'Get metadata for a file or folder' — a pure retrieval operation with no side effects.

Questions about get_metadata

What does the get_metadata tool do? +

Get metadata for a file or folder. It is categorised as a Read tool in the Yadisk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_metadata? +

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

What risk level is get_metadata? +

get_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_metadata? +

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

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

get_metadata is provided by the Yadisk MCP server (patr56/yadisk-mcp). 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.