get_source_id

Retrieve single source object details by ID.

SERVEROrigeneMCP SOURCEgentel-lab/origenemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/gentel-lab-origenemcp/get-source-id.md

WHAT IT DOES

What get_source_id does on OrigeneMCP

AI agents call get_source_id to retrieve information from OrigeneMCP 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_source_id is rated Low

This is a read-only query operation that fetches data by identifier. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial transactions. The low severity reflects minimal blast radius if misused by an agent — it can only retrieve existing information, not alter system state or trigger external actions.

From the tool's definition Tool description states 'Retrieve single source object details by ID' — a straightforward retrieval operation with no modification, deletion, or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_source_id safely

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

get_source_id Allowed

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

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

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

FAQ

Questions about get_source_id

What does the get_source_id tool do? +

Retrieve single source object details by ID. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_source_id? +

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

What risk level is get_source_id? +

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

Can I rate-limit get_source_id? +

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

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

get_source_id is provided by the Origene MCP server (gentel-lab/origenemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Origene, and thousands of servers like it.

This server

All 439 Origene 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 →