screenlog_process_model_get

Return the saved ProcessModel for a session (the structured 'what they did / how machinery is used' analysis).

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 11 required

What screenlog_process_model_get does on Yaver

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

ParameterTypeRequiredDescription
id string Yes

Parameters from the server's own tool schema.

Why screenlog_process_model_get needs a policy

Even though screenlog_process_model_get 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 screenlog_process_model_get

What does the screenlog_process_model_get tool do? +

Return the saved ProcessModel for a session (the structured 'what they did / how machinery is used' analysis). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does screenlog_process_model_get accept? +

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

How do I enforce a policy on screenlog_process_model_get? +

Register the Yaver MCP server in PolicyLayer and add a rule for screenlog_process_model_get: 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 screenlog_process_model_get? +

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

Can I rate-limit screenlog_process_model_get? +

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

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

screenlog_process_model_get 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.