get_ai_metadata

SERVERZype Com SOURCEzype/zype-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/get-ai-metadata.md

WHAT IT DOES

What get_ai_metadata does on Zype Com

AI agents call get_ai_metadata to retrieve information from Zype Com 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
`video_id`	string	Yes	The video ID (required)
`session_id`	string	Yes	The AI metadata session ID for one attribute (required)

Parameters from the server's own tool schema.

RISK

Why get_ai_metadata is rated Low

Even though get_ai_metadata 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_ai_metadata safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ai_metadata, this is the rule to start with:

get_ai_metadata Allowed

get_ai_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_ai_metadata": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every get_ai_metadata call is checked against it from then on.

FAQ

Questions about get_ai_metadata

What does the get_ai_metadata tool do? +

Get one AI metadata suggestion by session_id, including its generated value. Each session covers a single attribute. Use the session_id values returned by generate_ai_metadata. Read-only - viewing a suggestion does not modify the video. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.

What parameters does get_ai_metadata accept? +

get_ai_metadata accepts 2 parameters: video_id, session_id. Required: video_id, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_ai_metadata? +

Register the Zype Com MCP server in PolicyLayer and add a rule for get_ai_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 Zype Com. Nothing to install.

What risk level is get_ai_metadata? +

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

Can I rate-limit get_ai_metadata? +

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

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

get_ai_metadata is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zype Com, and thousands of servers like it.

This server

All 296 Zype Com tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →