You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're running GitHub Agentic Workflows on a self-hosted runner inside our corporate network. We have an internal REST API (not reachable from the public internet).
Is it possible for the agent to call that API directly — without wrapping it in a custom MCP server — simply by adding the internal hostname to network.allowed? Or is direct HTTP access from the agent to arbitrary internal endpoints not supported by design?
auto-answeredDiscussion received an automated response from the Agentic Workflows bot
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We're running GitHub Agentic Workflows on a self-hosted runner inside our corporate network. We have an internal REST API (not reachable from the public internet).
Is it possible for the agent to call that API directly — without wrapping it in a custom MCP server — simply by adding the internal hostname to network.allowed? Or is direct HTTP access from the agent to arbitrary internal endpoints not supported by design?
Beta Was this translation helpful? Give feedback.
All reactions