get_property

Load one property definition from Sanka for a given object family and property reference.

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/get-property.md

WHAT IT DOES

What get_property does on Sanka MCP Server

AI agents call get_property 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 get_property is rated Low

This tool retrieves metadata (a property definition) from Sanka for a given object family and property reference. It performs a simple read/lookup operation with no side effects, no data modification, and no external code execution. The blast radius of misuse is minimal—an agent could only access property definitions it is already authorized to query.

From the tool's definition Tool name 'get_property' and description 'Load one property definition' indicate a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_property 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 get_property, this is the rule to start with:

get_property Allowed

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

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 get_property call is checked against it from then on.

FAQ

Questions about get_property

What does the get_property tool do? +

Load one property definition from Sanka for a given object family and property reference. 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 get_property? +

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

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

Can I rate-limit get_property? +

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

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

get_property 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 →