New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

screen__get_title

[電影院時刻表與上映日資料庫]查單一作品:製作、發行平台、導演、首次公開日、上映時程與改期紀錄、初公開與最新官方預告、官方新聞;中文、英文、日文片名皆可(如 沙丘3、Avengers Doomsday、薬屋のひとりごと)。

SERVERAI 代理人任務中樞 SOURCEhttps://hub.penguindriver.com/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-penguindriver-hub/screen--get-title.md

What screen__get_title does on AI 代理人任務中樞

AI agents call screen__get_title to retrieve information from AI 代理人任務中樞 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
q string Yes

Parameters from the server's own tool schema.

Why screen__get_title is rated Low

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

Questions about screen__get_title

What does the screen__get_title tool do? +

[電影院時刻表與上映日資料庫]查單一作品:製作、發行平台、導演、首次公開日、上映時程與改期紀錄、初公開與最新官方預告、官方新聞;中文、英文、日文片名皆可(如 沙丘3、Avengers Doomsday、薬屋のひとりごと)。. It is categorised as a Read tool in the AI 代理人任務中樞 MCP Server, which means it retrieves data without modifying state.

What parameters does screen__get_title accept? +

screen__get_title accepts 1 parameter: q. Required: q. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on screen__get_title? +

Register the AI 代理人任務中樞 MCP server in PolicyLayer and add a rule for screen__get_title: 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 AI 代理人任務中樞. Nothing to install.

What risk level is screen__get_title? +

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

Can I rate-limit screen__get_title? +

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

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

screen__get_title is provided by the AI 代理人任務中樞 MCP server (https://hub.penguindriver.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on AI 代理人任務中樞, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AI 代理人任務中樞's. Pull the full record:

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.