Low Risk

get_record_share_link

Get a shareable link for a record.

Risk signalsHandles credentials or secrets (password)

Part of the FlowSheets server.

get_record_share_link is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE FLOWSHEETS →

Free to start. No card required.

AI agents call get_record_share_link to retrieve information from FlowSheets without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_record_share_link only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_record_share_link": {}
  }
}

See the full FlowSheets policy for all 36 tools.

Get this rule live on your own FlowSheets server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FLOWSHEETS →

View all 36 tools →

These attack patterns abuse exactly the kind of access get_record_share_link gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_record_share_link only ever does what you allow.

SECURE FLOWSHEETS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_record_share_link tool do? +

Get a shareable link for a record.. It is categorised as a Read tool in the FlowSheets MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_record_share_link? +

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

What risk level is get_record_share_link? +

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

Can I rate-limit get_record_share_link? +

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

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

get_record_share_link is provided by the FlowSheets MCP server (garfield-bb/hap_paas2025). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FlowSheets tool call.

Deterministic rules across all 36 FlowSheets tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.