get_ad_timing

View Ad Timing.

SERVERZype Com SOURCEzype/zype-mcp

Low RISK CLASS

Category Read

Parameters 33 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-ad-timing.md

WHAT IT DOES

What get_ad_timing does on Zype Com

AI agents call get_ad_timing 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
`id`	string	Yes	id (required)
`ad_timing_id`	string	Yes	ad_timing_id (required)
`data_source_id`	string	Yes	data_source_id (required)

Parameters from the server's own tool schema.

RISK

Why get_ad_timing is rated Low

Even though get_ad_timing 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_ad_timing 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_ad_timing, this is the rule to start with:

get_ad_timing Allowed

get_ad_timing 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_ad_timing": {}
  }
}

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_ad_timing call is checked against it from then on.

FAQ

Questions about get_ad_timing

What does the get_ad_timing tool do? +

View Ad Timing. 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_ad_timing accept? +

get_ad_timing accepts 3 parameters: id, ad_timing_id, data_source_id. Required: id, ad_timing_id, data_source_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_ad_timing? +

Register the Zype Com MCP server in PolicyLayer and add a rule for get_ad_timing: 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_ad_timing? +

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

Can I rate-limit get_ad_timing? +

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

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

get_ad_timing 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 →