lookout_get_run

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/lookout-get-run.md

WHAT IT DOES

What lookout_get_run does on Sanka MCP Server

AI agents call lookout_get_run to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why lookout_get_run is rated Low

Even though lookout_get_run 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 lookout_get_run safely

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

lookout_get_run Allowed

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

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

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

FAQ

Questions about lookout_get_run

What does the lookout_get_run tool do? +

Inspect one Sanka Monitor Motion run: status, approval state, the triggering signal, configured action inputs, and — for executed HubSpot landing-page actions — the provider result including created page IDs and URLs. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookout_get_run? +

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

What risk level is lookout_get_run? +

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

Can I rate-limit lookout_get_run? +

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

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

lookout_get_run is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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