studio_permission_prose

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 101 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/studio-permission-prose.md

WHAT IT DOES

What studio_permission_prose does on Yaver

AI agents call studio_permission_prose to retrieve information from Yaver 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
`app`	string	—	App display name for generated prose.
`path`	string	—	Repo/app root on the target machine. Defaults to agent cwd.
`what`	string	—	Plain-language use case.
`useCase`	boolean	—	Generate narrative prose for a real background task use case.
`manifest`	string	—	Explicit AndroidManifest.xml path.
`whatRuns`	string	—
`device_id`	string	—	Optional owned Yaver device id/name/alias whose agent has the repo.
`permission`	string	Yes	Permission or FGS type, e.g. FOREGROUND_SERVICE_SPECIAL_USE.
`progressText`	string	—
`completionText`	string	—

Parameters from the server's own tool schema.

RISK

Why studio_permission_prose is rated Low

The tool reads and analyzes AndroidManifest.xml file data and produces documentation output (prose, shot-list). This is a query/analysis operation with no capability to alter app state, execute commands, modify permissions, or cause destructive changes. The optional device_id parameter merely specifies where to read from (another Yaver machine), not what actions to perform.

From the tool's definition Tool performs 'Analyze AndroidManifest.xml for a permission' and 'generate Play Console prose plus a video shot-list'—purely analyzing an existing manifest file and generating documentation.

Risk signalsAccepts file system path (path) · High parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs studio_permission_prose safely

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

studio_permission_prose Allowed

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

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

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

FAQ

Questions about studio_permission_prose

What does the studio_permission_prose tool do? +

Analyze AndroidManifest.xml for a permission and generate Play Console prose plus a video shot-list. Good for FOREGROUND_SERVICE_SPECIAL_USE and third-party app permissions. Optional device_id runs on another owned Yaver machine that has the repo. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does studio_permission_prose accept? +

studio_permission_prose accepts 10 parameters: app, path, what, useCase, manifest, whatRuns, device_id, permission, progressText, completionText. Required: permission. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on studio_permission_prose? +

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

What risk level is studio_permission_prose? +

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

Can I rate-limit studio_permission_prose? +

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

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

studio_permission_prose is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

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